Policy builder
A policy defines how Astralis handles a privacy request. With DSR Policies (beta) (dsrPolicyWorkflows) enabled, go to Privacy requests > DSR policies in the Admin UI, or DSR > Policies in the Astralis UI, to create a policy or edit an existing one. The beta adds a Configuration tab and the Request type label and Workflow fields to the policy form. Turn the flag on under Settings > About Astralis using an administrator account with permission to manage feature flags. See feature flags.
Choose a label and workflow
Select Create policy, then complete these fields:
| Field | What to enter |
|---|---|
| Name | An internal name for the policy. Its key identifies it in request submissions and task conditions. |
| Request type label | The right shown in Request Manager, such as Right to appeal. Optional for built-in workflows; required and nonblank for Custom. |
| Workflow | The execution behavior, such as Access, Erasure, or Custom (custom). |
| Execution timeframe | The number of days allowed to fulfill requests under this policy. |
Select Create to save. Reopen the policy to review its workflow. Editing an existing policy lets you update its label; its workflow cannot be changed in the edit form.
A label does not have to match a workflow name. For example, an access policy may carry the label Data disclosure. Policies may share labels. Requests read the label from the current policy, so renaming it relabels all of that policy's existing requests, closed ones included, in Request Manager. See request types.
Create a custom manual workflow
- Create a policy named Appeal review, set Request type label to Right to appeal, and select Custom as its workflow.
- Under Integrations, create a Manual Task integration or open an existing one. Add a Custom field under Configure Tasks, of type Text or Attachment, such as a text field labelled Appeal review notes.
- Assign the users who will complete the task.
- Open the policy's Fulfill card, select Choose integrations, and pick this Manual Task integration. Only the integrations a policy chose raise tasks for it. Once a policy has chosen, an integration it did not choose raises no task for it, even if that integration has a Custom field.
- Configure a Privacy Center action to reference the policy key, or submit a request against the policy through the API.
- Check that the request reaches Requires Input, that the manual task is available, and that Right to appeal appears on the Request Manager list and detail page.
Step 4 is required. A custom policy must choose its integrations: it never follows the default integrations, and a policy-key condition is not a substitute.
A custom request is handled through manual tasks. The Custom workflow does not retrieve data, run erasure, or produce an access package. A label describes the right; it does not bind a policy to an integration. What binds a policy to an integration is the policy's own integration choice on its Fulfill card.
A request for a custom policy is refused at creation when the policy hasn't chosen its integrations, or when none of the integrations it chose has a Custom task. Choose at least one integration with a Custom task before you point a Privacy Center action at the policy.
Feature flag behavior
The label and workflow controls are available behind dsrPolicyWorkflows. With the flag off, the policy form uses the existing Request type field and does not offer custom policy creation. The API also requires the flag to create a custom rule. Turning the flag off does not remove existing custom policies or stop requests already using them; it is not a cancellation mechanism.