I am very new to Salesforce, so apologies if my use of terms is not correct.
I am using Lightning Knowledge
I have enable and setup Knowledge Base and added FAQ articles and have added Question and Answerr fields to those articles.
I have setup the field visibilty so they are visible to all user including "Read Only" users (I could not find anything specific for Guests, should there be?)
So as far as I can tell the field permissions on the Question and Answer fields is correct.
I create articles and enter my values for my "Question and Answer fields" but when I go to my public site to view the FAQ, I only see the content of the Title and URL Name fields. I do not see my Question and Answer Fields.
If I login and view the articles via the public site, I do see the Question and Answer values.
I would very much appricaite it if anyone could point me in the right direction for trying to figure this out. I have googled but cannot seem to find anything that talks about guest users and field visibilty that has helped me.
Many Thanks
Derek
Yes, guest user is still an user. There's hidden user account (which acts as "created by" when you make new Case for example) and Profile which you might have to edit. It doesn't show up on normal list of profiles (but for example the Id can be queried and once you know Id you could construct the url yourself).
If you're using an Experience Cloud (aka Community) go to your site's Builder and the links will be at the bottom.
If you're using Sites - it should be in Site's config.
I had the exact same issue, but did see the solution documented in the previous comments.
In your community navigate to Settings
Select General
Click link under Guest User Profile
Scroll down to Field-Level Security
Click View for Knowledge
Click Edit
Check the Read Access box for the fields which are not displaying
Click Save
Related
I have an object "Project" that has a lookup field "Account__c". In the Salesforce experience builder, I want to have a link in the Project Detail page to the connected Account.
Something like "Go back to your account".
But I tried various links like "https://our webite/s/account/{!recordId.Account__c}"
I know that this: "https://* our website"/s/project/{!recordId}" works so I feel that there is a solution to this. I hope someone can help me.
Thanks in advance
I assume you're using standard detail page components and are looking to build a formula field to expose the linked Account URL?
/s/account/{!Account__r.Id} should do the trick as a relative URL.
So I'm completely new to Salesforce Communities and working with the Experience Builder which is where I think this task would need to be done.
I want to display a list of Users in the Community (specifically only ones associated with the same Account as the current User) showing a certain set of fields and allowing in-line edits.
I see there's already a set of pages for User list, profile, and related list, but the User List page is blank by default. I found the Record List component for Experience Builder, but it does not appear to support User.
I'm considering making a Lightning Component that displays my table of Users to then use as a component in Experience Builder, but I'm not sure how involved of a process that would be or if there is a more straightforward approach.
How can I go about making this?
(If it matters, when I first made the Community I believe I selected "Customer Service")
This seems like a really simple requirement for a blogging app or CMS:
How do you automatically make the logged-in user the author of a wagtail page? For example, if I log in as "Bob" and type a post, the author should automatically be "Bob".
Normally I would simply write it into my Django views but since I'm using Wagtail I expect it to be in the main package. However, the docs don't mention it, and the official demo seems to imply that authors must be chosen from a dropdown select box, which means any author can pretend to be anyone else!
We access the People object with an inline panel that references the
ParentalKey's related_name in BlogPeopleRelationship.
Is there a feature I've missed?
The user who created a page is available as the property owner:
http://docs.wagtail.io/en/stable/reference/pages/model_reference.html#wagtail.core.models.Page.owner
This is used within Wagtail for permission checks (a user with 'add' but not 'edit' permission can edit pages that they have created themselves), but it can also be displayed on your site front-end as the page author if you so desire.
Currently the list component just shows all items (links) but I'm trying to find a way to hide a certain links, based on the logged in user role.
It seems that [Plugin:Equals] and [Plugin:NotEquals] tags allow us to conditionally show/hide the links, so I think this is probably the approach can try. But when it comes to getting the user access role/group info, I feel a bit stuck.
For now, I am only able to find the following fields that are available for use:
${wp.user.cn}
${wp.user.sn}
${wp.user.uid}
${wp.user.preferredLanguage}
And the online document doesn't say much either. https://www.ibm.com/support/knowledgecenter/SSYJ99_8.5.0/dev-theme/themeopt_el_bean_user.html
So is it possible to get the assigned user access group via wp.user? Or perhaps there are other ways to show/hide the links in the list component?
Not via wp.user you would need to use the access control model, but would be better using the attribute based security
WCM Security will hide any links the current user doesn't have access to - be it a Site Area, Content Item / Link. Check your security on the objects which shouldn't be showing. You'll most likely find you haven't restricted access.
To resolve this problem on my own, I started out by installing Profile2 and Profile2 registration. At no point was I able to generate a page based on the user name (eg, {domain}/private/register). I figured it was not coming up b/c I checked off that anonymous users could not see published pages (which is a site requirement). However, I might have done something wrong but I went over the instructions several time and I don't think I made a mistake. Any suggestions would be helpful.
I think you may have to create a new content type, similar to the normal story or article types, and publish restricted content as the new page type. Apply the access restriction to this content type, and leave the default content types alone.