1. Temporary Permission Use Cases

If an approver in a Business Process lacks data access, they cannot view the business record and therefore cannot complete the approval task.

Without temporary permissions: the record owner adds the approver to the object Related Teams so the approver gains access to the data.

With temporary permissions: configure temporary permission rules on the object; the system automatically grants temporary access according to the configured rules.

1. Configure temporary permission rules with start time and revoke time; grant Read-Only or Read/Write access.
2. Disabling a temporary permission rule revokes any previously granted temporary permissions.
3. Administrators can revoke temporary permissions as needed from the Authorized List.

2. Temporary Permission Concept

Temporary permissions grant access to approvers of pending Business Processes who otherwise do not have permission to the pending records. Administrators configure the duration (number of days) and the access level (Read-Only or Read/Write).

Temporary permission rules do not apply retroactively to historical records.

3. When Permissions Take Effect

When temporary permissions are enabled, new process instances created afterward receive temporary access according to the permission rule. Process instances created after temporary permissions are disabled will not receive temporary access. If users require long-term access to data, configure proper data permissions and data sharing rules or add users to Related Teams.

Note: Temporary permissions do not apply to process instances created before temporary permissions are enabled.

4. System Impact of Temporary Permissions

After enabling temporary permissions, approvers who previously had no access will be able to view record details in their task list because administrators granted temporary access. Administrators must configure data permissions accurately to maintain proper governance.

Temporary Permissions List

You can manually revoke permissions.