Account Structure and Sub-Account Management

Note: Only Administrators have access to this area.

Sub-Accounts can be created under your Account or under any other Sub-Accounts within your Account.
Sub-Accounts are useful if you manage Event(s) for other client organizations or divisions of your company, and you would like to keep their Event(s) and Registration data separate from that of other Accounts.

Each Account or Sub-Account contains its own database.
Even if Accounts have the same name or codes, items such as Custom Event Data, Custom Profile Data, Content Blocks, Display Fields, and Profiles are unique to the Account.
These items are held separate from those same items in other Accounts.
Roles, Tags, and some other areas can be set to use the settings/fields from the Parent Account.
A Sub-Account has its own separate database of Events.
All information in a Sub-Account is visible to any Users with access to the Parent Account.
Sub-Accounts can be useful within large organizations in keeping Event data organized by department or division.
Sub-Accounts can be useful within a smaller business by keeping Events and data separated by client.
Events are always associated with an Account or a Sub-Account.
Since each Account and Sub-Account has its own Profiles and Events databases, it is important that Accounts be arranged logically.
The System Administrator should consider how best to structure the Accounts.

User Accounts can be set up at the Sub-Account level.
Users with access at the Parent Account level will see a drop-down menu in the upper left of the screen with the list of Sub-Accounts to choose from.

Was this article helpful?

Have more questions? Submit a request