Non-Versioned Security

Assign permissions, data access sets, and user groups that aren't subject to the project lifecycle.

Overview

Administrators use versioned and non-versioned workflows to administer Visier tenants. Versioned workflows happen in projects where you define and edit the solution separately from the current production version. For more information, see Projects. Non-versioned workflows happen in the global workspace and through Visier APIs where you define and edit the solution immediately without updating the production version.

You have a choice between versioned or non-versioned security in Visier. Versioned security is created and assigned to users within projects and results in a new production version of your solution. Non-versioned security is created and assigned to users using Visier APIs and does not change the production version.

When to use non-versioned security

Because non-versioned security eliminates the release of new production versions, it prevents frequent version changes that make it harder to roll back or find a version causing issues in your tenant. You might choose to use non-versioned security for frequent, small-scale security updates and rapidly changing organizational structures.

View non-versioned security

You can see a list of all non-versioned permissions, data access sets, and user groups in the global workspace. On the global navigation bar, click Tenant > Security. The list is read only. To edit non-versioned security, you must use the Permissions API or User Groups V2.

If the list is blank, your tenant doesn't have any non-versioned security artifacts. The following screenshot shows a tenant with one non-versioned permission.

You can identify non-versioned permissions in a user or user group by the icon, as shown in the following screenshot.

Use Visier APIs to assign security

You can choose whether the permissions, data access sets, and user groups are versioned or non-versioned.

• Versioned: Associated with a new production version that releases any security changes to production. Created in a project or by using the Permissions API and User Groups V2 API with the NonVersioned header omitted or set to false. For more information about the NonVersioned header, see API Headers.
• Non-versioned: Take effect immediately and do not result in a new production version. Created by using the Permissions API or User Groups V2 API with the NonVersioned header set to true.

  Caution: Non-versioned permissions can only use security filters defined within the permission using the memberFilterConfigs parameter.

Versioned and non-versioned methods cannot be mixed.

• If you want to modify an existing versioned permission, data access set, or user group, you can only do so through versioned workflows, such as in a project or with the NonVersioned header omitted or set to false.
• If you want to modify an existing non-versioned permission, data access set, or user group, you can only do so using the Permissions API or User Groups V2 API with the NonVersioned header set to true.

Similarly, versioned and non-versioned artifacts cannot be mixed. For example:

• Assign versioned data access sets to versioned permissions.
• Assign non-versioned permissions to non-versioned user groups.

For more information, see Permissions API and User Groups V2.