System Permission Hierarchies

As superusers it's hard to put ourselves in client's shoes so there's been confusion about who can see what. Here's a breakdown of what different CRM, Accounts, and Drip permission settings allow. 

 

 

CRM:

There's a hierarchy of users that can log in as users. Surprisingly Owners can't log in as other admins, but Admins and Owners can change eachother's permissions. 

Possible CRM Accounts Issues:

  • Problem: Owners don't explicitly have all permissions in the CRM. All Except "Enabled" can be revoked, which causes some confusion. 
    • Solution: Always double check permissions if something isn't working. 

 

ACCOUNTS:

The names on the permissions in Accounts are pretty straightforward, but there's a distinction between different types of users, and the level of MCP access that's granted.

Possible Account Permission issues:

  • Problem: Creating a user in accounts (such as a Partner) doesn't create a user in the CRM, but creating a user in the CRM creates an account. 
    • Solution: Create User in CRM with email address from account.
  • Problem: If an owner already exists, but has a permission disabled at the time they take command, that permission will stay permanently locked off until the owner status is removed. 
    • Solution: Assign a new owner, update the permissions, and then revert ownership. 
  • Problem: Returning Clients have issues logging in properly with a disabled site. 
    • Solution: Fully disable old Site/CRM and remove all user connections from CRM/Accounts
  • Problem: Some accounts have too many permissions such a Todd's original account, and can no longer log in.
    •  Solution: Don't be greedy; TODD.
  • Problem: The Website: Settings checkbox currently allows some access inside /admin/ in the new view that wasn't available in legacy. This should only allow access to site-level MCP. 

 

DRIP:

Drip only really has 2 settings, Super, Not-Super, or None. 

Super View:

Not-Super View:

None View: