Who is this article for?

Administrators and Module Developer learning about roles and object access.

A Module Developer license and Area access is required.

Every record is attached to a Reporting Authority (RA) and every Role associated with a User and Team is also attached to a RA. RA's give users access to the data, while Roles give users access to objects. They are the foundation of the platform's security. User roles are assigned within a given RA. Many customers may only have one RA, but some configurations will require more than one.

The Reporting Authority screen has three parts to it:

• On the left, is the hierarchical structure of the RAs.
• In the Details sections, the time zone can be configured, per RA. The parent RA can also be configured in the Details region.
• In the Sequences sections, specific sequences can be defined per module. For example, if an RA represents a division and for each division there were unique identifiers, at the corporate level, they could easily differentiate between the divisions based on the sequence of identifiers.

Modifying a RA can have consequences
Reporting Authorities are set up and fully managed by the module developer. Administrators should not modify Reporting Authorities without first discussing the changes with a Technical Account Manager (TAM) to understand the potential impacts. This shortcut is available to users with the Area Administrator role.

For additional access and security information visit Getting started with security.