I. Temporary Permission Use Cases

When workflow approvers lack data access permissions, they cannot view business data and thus cannot complete their assigned tasks.

Alternative Solution Without Temporary Permissions:
The owner can add approvers to the Related Teams of the object, granting them access to the data.

Solution Using Temporary Permissions:
Configure temporary permission rules per object. The system automatically grants temporary permissions based on these rules.

1. Configure Temporary Permission Rules:
   • Set the permission activation and expiration time.
   • Grant read-only or read-write permissions.
2. Disabling Temporary Permission Rules:
   • Revokes all previously granted temporary permissions.
3. Manual Permission Revocation:
   • Admins can manually revoke temporary permissions from the authorized list as needed.

II. Temporary Permission Concept

Temporary permissions are granted to approvers or Business Process handlers who lack access to the data required for pending tasks. Admins can configure the duration of these permissions (e.g., days) and the access level (read-only or read-write) based on company needs.

Note: Temporary permissions do not apply retroactively to historical data.

III. Data Activation Timing

• Enabled Temporary Permissions:
  Newly generated workflow instances will apply temporary permissions based on the configured rules.

• Disabled Temporary Permissions:
  New workflow instances will not use temporary permissions. For long-term data access, configure proper data permissions, data sharing, or Related Teams.

Important: Temporary permissions do not apply to workflow instances created before enabling the feature.

IV. System Impact of Temporary Permissions

Once enabled, approvers without original data permissions can view task details in their pending workflows due to the temporary permissions configured by admins. From a management perspective, ensure data permissions are accurately configured.

Temporary Permission List

Manual Permission Revocation