MENU
The administrator has created new users for ten new employees at Northern Trail Outfitters.
Why are these users unable to access the account object in the Salesforce or?
40 comments · newest first
LE
Lelia
11 months ago
Not sure about that, seems odd for new users.
WI
Winfred
11 months ago
Wait, are the org-wide defaults really set to private?
AN
Annabelle
12 months ago
I think it could also be the sharing rules.
LA
Larae
12 months ago
I agree, it's definitely a permissions issue.
HU
Hubert
1 year ago
They probably need permission to the Account object.
DE
Delila
1 year ago
Sharing rules were mentioned in our last review session, but I can't remember if they apply to new users right away. This is tricky!
BE
Bernadine
1 year ago
I recall that roles can affect access too, but I'm not confident if that's the main reason here. Maybe it's a combination of factors?
AN
Annett
1 year ago
I'm not entirely sure, but I feel like it could also be about the organization-wide defaults being set to private. That sounds familiar from the practice questions.
LE
Leslee
1 year ago
I think the issue might be related to the users' profiles needing specific permissions for the Account object. I remember something about that in the study materials.
TE
Teri
1 year ago
Ugh, permissions questions are the worst. I'm just going to guess and hope for the best on this one.
GL
Gladys
1 year ago
Hmm, I'm a bit unsure about this one. I'll need to review the sharing rules and role hierarchy to see what might be causing the access issue.
PO
Polly
1 year ago
This seems like a straightforward permissions issue, so I'll start by checking the users' profiles and the organization-wide defaults.
BI
Billy
1 year ago
Okay, I think I've got a good handle on this. The key is to identify whether the problem is with the user profiles, sharing settings, or role hierarchy. I'll methodically go through each option.
LA
Lashon
1 year ago
Okay, I think I've got this. The key is to configure the switch port to trust the DSCP markings from the IP phone, so the data traffic gets the same priority as the voice traffic. I'll go with Option B.
NI
Nickie
1 year ago
Hmm, this seems straightforward. I think creating a Teams policy and assigning it to the users is a good approach to prevent temporary employees from using the private chat feature.
VI
Vicki
1 year ago
Honestly, I'm just hoping the admin remembered to turn on the 'Visible to All' feature for the Account object. You know, just in case they forgot the whole 'permissions' thing.
OM
Omer
1 year ago
D) Organization-wide defaults are set to private.
GO
Goldie
1 year ago
C) Users' roles are low on the role hierarchy.
KA
Kayleigh
1 year ago
B) Users' profile requires permission to the Account object.
LE
Lelia
1 year ago
A) Users' profile requires a sharing rule for Accounts.
AR
Art
1 year ago
What, no option for 'All of the above'? That's the real correct answer here. Salesforce just loves to make things complicated, don't they?
HE
Henriette
1 year ago
C) Users' roles are low on the role hierarchy.
MA
Major
1 year ago
B) Users' profile requires permission to the Account object.
NI
Nieves
1 year ago
A) Users' profile requires a sharing rule for Accounts.
HE
Helene
2 years ago
This is a tricky one, but I think the answer is B. The users' profile needs to have the 'Read' permission on the Account object. No profile, no access!
HE
Heidy
1 year ago
C) Users' roles are low on the role hierarchy.
WI
Wilburn
1 year ago
B) Users' profile requires permission to the Account object.
KA
Kayleigh
1 year ago
A) Users' profile requires a sharing rule for Accounts.
CH
Cherelle
2 years ago
I'm going with option C. The users' roles are low on the role hierarchy, which means they don't have the necessary access to the Account object. Gotta love those role hierarchies!
DO
Dorathy
2 years ago
Ah, I see! It's definitely option D. The organization-wide defaults are set to private, so the users won't be able to access the Account object unless the admin sets up the appropriate sharing rules.
MA
Marvel
1 year ago
D) Organization-wide defaults are set to private.
JU
Julieta
1 year ago
C) Users' roles are low on the role hierarchy.
DI
Diego
1 year ago
B) Users' profile requires permission to the Account object.
LI
Lindsey
1 year ago
A) Users' profile requires a sharing rule for Accounts.
RE
Remedios
2 years ago
Hmm, I think it's option B. The users' profile must have the necessary permissions to access the Account object. No need for a sharing rule if the profile itself doesn't have that permission.
JO
Jordan
2 years ago
Maybe the administrator forgot to assign the correct permissions to the users' profiles. That could be why they can't access the Account object.
MA
Marvel
2 years ago
I agree, option B makes sense. Without the permission to access the Account object, they won't be able to see it.
NI
Nieves
2 years ago
Maybe the organization-wide defaults are set to private, causing the issue.
VI
Viva
2 years ago
I agree with Billy. Without permission to the Account object, they won't be able to access it.
BI
Billy
2 years ago
I think the users' profile requires permission to the Account object.