define user types and associated permissions and restrictions

[connorscarolyns]

The system does not have the concept of "role"; instead, it's more granular, and a diverse set of permissions can be applied to any user. This makes a fantastically flexible system but also makes it difficult to give the appropriate permissions to certain user types.

We need to define each type of user with access to our system and what they should and should not be able to do.

So far, we have:

• Basic account holder
• Publishing account holder
• Account Administrators
• System administrators

In the future, we should consider the following:

• Super administrators
• Support administrators
• Team accounts
• Team administrators

Not sure if all of these are needed, but a good look at our road map and what types of users we'll need to support should help guide us

[connorscarolyns]

@srtalbot @Abi-Nada I believe a document already started satisfies this issue. Is that correct? If so, we can close it.