Although C is the best answer, technically speaking, the fileds are automatically located on the Page Layout under the Details Section. The Admin only needs to re-arrange depending on Record Types etc. So actually Setting Permission Sets would be the next Step from the choices available.
I don't think so. Any fields that are created from the Schema Builder will not be automatically added to the page layout. Even if you give all the necessary permissions for access, if the field is not included in the page layout, the user cannot access it
As I read https://ideas.salesforce.com/s/idea/a0B8W00000GdehLUAR/security-options-for-schema-builder
Response for the Idea from salesforce:
I'm happy to be able to announce that in Summer '13, the defaults for field level security on new fields created in Schema Builder will be the same as the defaults for new fields created in the custom field wizard. Profiles that are not cloned from portal/partner profiles will be able to see the fields and edit them (unless of course the field is read-only).
See the Summer '13 release notes for more details on this and other core platform features!
After reading this i understood that default visiblity is given to most of the profiles
Agree with Boris, Shouldn’t it be D , D. Create a permission set for access to the object and fields.This is the most critical step to ensure that users can actually access the object and its fields. Without permission, the fields won’t be visible even if added to the layout.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
[Removed]
Highly Voted 2Â years, 1Â month agop4wix
2Â years, 1Â month agolena989
1Â year, 10Â months agoBorisBoris
Highly Voted 1Â year, 9Â months agoBassza
8Â months, 1Â week agoSreeteja123
1Â year, 2Â months ago92b6348
Most Recent 6Â days, 17Â hours ago