Gotransverse UI Security Roles, Authorities, and Limits

Security authorities define the level of access a user has to specific applications, modules, menu options, or actions within Gotransverse by making menu icons and actions visible within the Gotransverse interface. The authorities can be at the application level, at the application’s module level, or at the action within a module level. The Gotransverse security architecture is illustrated in the following graphic:

User Roles and Authorities Architectural

The three levels of authorities include:

• Application Level Authorities — Controls whether an application displays in the Gotransverse application menu , and, if no lower-level authorities are created, they can determine if a user can either perform all actions (full access) or no actions (read-only) within the specific application. The following security authorities are examples of read-only or full access:

  Currently, there are read-only access security authorities only for the Customer Billing, GTV-Connector, and Revenue Management applications.

  • Customer Billing - Full Access: User has full access to all the Customer Billing application’s modules (Customer Billing Full Access Security Authorities).

  • Customer Billing - Read-only Access: User can only view the Customer Billing application’s modules (Customer Billing Read-Only Access Security Authorities).

  • GTV – Connector Full access: User has full access to all the GTV-Connector application’s modules (GTV Connector Security Authorities).

  • GTV – Connector Read-only access: User can only view the GTV-Connector application’s modules (GTV Connector Security Authorities).

  • Revenue Management (GL) — Full access: User has fill access to all the Revenue Management application’s modules (Revenue Management Full Access Security Authorities).

  • Revenue Management (GL) — Read-only access: User can only view the Revenue Management application’s modules ( Revenue Management Read-Only Security Authorities).

  • Payment Matching (RMS) - Full access: User has full access to all the Payment Matching application’s modules (Payment Matching Security Authorities).

  • Product Catalog - Full Access: User has full access to all the Product Catalog application’s modules (Product Catalog Security Authorities).

• Area/Module/Section Level Authorities – Adds controls to specific areas, modules, or sections of an application that a user could see or have access to. The following security authorities are examples of authorities for specific area, module, or section:

  • Customer Billing — Full access to the Customer Management area: User has full access only to the Customer Billing application’s Customers, Orders, Services, Invoices, and Payments modules (Customer Billing Full Access Security Authorities).

  • Customer Billing — Full access to the Invoices section in Customer Management area: User has full access to the Customer Billing application’s Invoices module. (Customer Billing Full Access Security Authorities).

  • Revenue Management (GL) — Full access to the Run Manager area: User has full access to the Revenue Management application’s Run Manager module (Revenue Management Full Access Security Authorities).

  • GTV Connector Integration — Run: User can schedule and create Integration runs in the GTV-Connector application (GTV Connector Security Authorities).

• Individual Action Level Authorities — Adds controls to specific actions that a user could perform within an applications’ area, module, or section. The following security authorities are examples of authorities for specific actions within a module:

  • Customer Billing — Invoices — Edit Invoice: User can see the Edit option under the Invoice drop-down menu of a selected invoice and the Edit option in the Actions column in the list of invoices for a billing account (Customer Billing Individual Action Level Security Authorities).

  • Revenue Management (GL) — Create Chart of Accounts: User can see the option Create Chart of Accounts in the Setup action menu in the Revenue Management application’s Setup module (Revenue Management Individual Action Level Security Authorities).

     

In addition, a user can configure limits for a specific action on certain action-level authorities. Limits allow maximum or minimum values to be set or to, potentially, limit the selection options that a user with the specific limit can make with the action. An example of a limit:

Example Limit

Action	Condition	Parameter 1	Parameter 2
Revenue Management (GL) - Create Manual Journal Entry	Conditional	Currency = EUR	Total Debit - Actual >= 1000

For the action of creating a manual journal entry in the Revenue Management application, users with this limit would be prevented from creating manual journal entries in the Euro(EUR) currency with values that, when the total debit is subtracted from the actually debit, are greater than or equal to 1,000 EUR.

 

 

 

 

Topic updated: 03/2024.