Authorization Workspace Settings

  • Updated on Jun 22, 2025
  • Published on Oct 1, 2023
  • 1 minute(s) read
Prev Next

Each Workspace has its own Settings screen which displays the settings for that Workspace. For information on creating and maintaining multiple Workspaces, see Managing Workspaces.

On the Authorization Workspace Settings screen, you have the following tabs:

  • Details
  • Permissions
  • Request Attributes

Details

On the Details screen of the Authorization Workspace, you can:

  • View and change the Workspace name
  • View and change the Workspace description
  • Set and change the Workspace Logo URL
  • View the unique Workspace ID
  • View the unique Environment ID

Permissions

The Permissions tab enables you to apply access rights to various levels of the Platform. There are two levels of access permissions: 

Admins have full administrative capabilities within the Environment to create, modify, and delete entities at that level

Viewers have access to a full view of all data-related objects managed within the Environment.

Note: Permissions can only be defined when using an external IDP.  Changes affecting Permissions may take up to 15 minutes to take effect in the Platform.

For more information, see  Platform Permissions.

Configuring Authorization Workspace Settings

To access and edit the Authorization Workspace Settings:

  1. Click the Authorization Workspace settings icon (Settings Icon). The Authorization Workspace Details screen is displayed.
  2. Click Edit. The fields of the currently displayed tab become editable. You can edit the Name and the Description fields.
  3. After you change a setting value, click Save.

Request Attributes

Request Attributes are used to pass additional context into the PDP for Policy evaluation. With the introduction of API mappers for Request Attributes, you can define how each parameter should be resolved during Runtime. These mappers specify the Attribute value source, enabling dynamic and flexible handling of request data. This allows Policies to react to varying Runtime conditions without requiring manual updates or static configurations.

This capability is particularly useful in scenarios where request parameters must be evaluated against external data sources. For example, in a healthcare setting, access to insurance data is controlled using request-based mappings or contextual data from the request and must be dynamically fetched based on user access requests.

For more details, see Request Attributes in the User Portal or Working with V5 Endpoint for API Access in the Developer Portal.