Source: https://docs.amadalis.ai/reference/copilot/account-and-privacy/

# Copilot: Account, team and visitor privacy

Open **Copilot** in the site admin and describe the result you want. Use the tables below to check the requests in this area, their approval steps and their available Undo.

Checked against the product’s code on 7 November 2026.

Account requests check your current account role. Some require the owner; others permit an Admin. Team requests act through your account’s Team controls.

In these account and privacy requests, a token is a credential for a connected service’s permitted requests. A [theme token](https://docs.amadalis.ai/reference/glossary/#token) is a design value instead. Opening the single sign-on, two-factor authentication, automatic team membership setup or billing screen only opens that screen. It does not complete the setup or disclose a secret in chat. Granting support access and disabling login or connection credentials need approval and have no automatic Undo.

Visitor erasure permanently removes the data within its stated scope. Orders keep their checkout name and email; form submissions need separate erasure. Visitor events are kept with no limit until you set a retention period. Once you set one, events older than it are deleted on the site’s regular scheduled run, but only after an archive export has covered them. An export download already taken cannot be recalled. Backup tools do not provide a customer restore request in the checked code.

Revoking a support grant stops new entries and ends its open session on the next request after the grant check refreshes, within 30 seconds. At expiry, the next request ends the session. The team session policy is checked on the Praxis account and inside open site admin sessions. See [Account Security](https://docs.amadalis.ai/account/security/#team-session-policy) for the refresh timing and policy-read failure limits.

In the tables, **Yes** under approval means a separate approval is required before applying the request. **Available** under Undo means the request can be reversed. The specific receipt must offer **Undo**; it can be limited by the input, later changes or the state that was saved. **No** means this request provides no automatic Undo. Reading a fact has nothing to undo.

These are plain-language descriptions of requests, not text you must type exactly. Your role, configured connections and site capabilities determine which requests are available. See [How copilot requests are governed](https://docs.amadalis.ai/reference/copilot/).

## Your account

| Request | Approval | Undo |
| --- | --- | --- |
| Download your account Security log in your browser | No | No |
| Open the owner’s billing screen | No | No |

| Open the owner’s site or whole-account closing steps | No | No | | Read the closing status | No | No | | Stop an eligible site or account closing as its owner | Yes | No | | Approve an imported account claim | Yes | No | | Send an imported account claim email | Yes | No | | List imported account claims and their states | No | No | | Attach a custom domain to your site | Yes | No | | Clear a redirect on a custom domain | Yes | No | | Detach a custom domain from your site | Yes | No | | List your custom domains and their status | No | No | | Recheck a custom domain’s DNS and certificate status | Yes | No | | Choose your site’s primary custom domain | Yes | No | | Redirect one of your custom domains | Yes | No | | Read your account role, sites and plan status | No | No | | List details of tokens used to create team memberships | No | No | | Open the team provisioning screen | No | No | | Revoke a team provisioning token | Yes | No | | Read your team’s session and sign-in policy | No | No | | Open the network address settings | No | No | | Change your team’s session and sign-in policy | Yes | No | | Open the single sign-on settings | No | No | | Disconnect a single sign-on connection | Yes | No | | List single sign-on connection details | No | No | | Grant support access to your account | Yes | No | | List your support access grants | No | No | | Revoke a support access grant | Yes | No | | Open the two-factor settings | No | No |

## API tokens

Site API tokens obey the team’s applicable network, membership and two factor rules, with the [token checks and read-failure limits](https://docs.amadalis.ai/account/site-access-and-settings/#personal-api-tokens). Session lifetime and idle timeout do not apply to tokens.

| Request | Approval | Undo |
| --- | --- | --- |
| List API token details | No | No |
| Revoke an API token | Yes | No |

## Backups

Only an Admin can manage backups. Taking and downloading a content backup are unavailable on this site’s database; those requests are refused. This is separate from a whole-site restore arranged through support.

| Request | Approval | Undo |
| --- | --- | --- |
| Delete a backup archive | Yes | No |
| Change backup configuration | Yes | Available |
| Create a backup | Unavailable | No |
| Download a backup archive | Unavailable | No |
| Read backup configuration and status | No | No |

## Consent policy

Ask how many recorded visitors personalization reached by country. This read uses today’s policy to explain the country’s rule; it cannot measure the share of all visitors, because refusals and Global Privacy Control are not in those records.

| Request | Approval | Undo |
| --- | --- | --- |
| Read the site’s consent policy | No | No |
| Read recorded personalization reach by country | No | No |
| Change the site’s consent policy | Yes | Available |

## Exports and retention

| Request | Approval | Undo |
| --- | --- | --- |
| Export selected visitor datasets | Yes | No |
| Set an automatic data export schedule | Yes | Available |
| Clear the automatic data export schedule | Yes | Available |
| Find an export file on the Exports screen | No | No |
| List your export runs and their status | No | No |
| Set a visitor event retention period | Yes | Available |

Only an Admin can download export files. Open **Privacy & Data** > **Exports** > **Run history** > **Downloads** in your signed-in browser; the copilot does not print a download link in chat.

## Passkeys

| Request | Approval | Undo |
| --- | --- | --- |
| Delete a passkey | Yes | No |
| List passkey metadata | No | No |

## Self-signup by email domain

An email domain can let people join with a chosen role up to Editor. For Admin access, invite the person from **Team** in your Amadalis account. A new rule above Editor is refused before an approval card is offered. An older rule stored as Admin stays stored that way, but new signups under it join as Editor.

| Request | Approval | Undo |
| --- | --- | --- |
| Let people at an email domain create their own account with a chosen role | Yes | Available |
| List the email domains that can sign up | No | No |
| Stop an email domain from signing up | Yes | Available |
| Change an email domain’s signup role or switch it on or off | Yes | Available |

**Undo limit.** The copilot cannot restore a deleted Admin domain rule or raise a lowered rule back to Admin. Switching an existing Admin rule off or on can be undone while its saved state still matches.

## Your team

For invitations and role changes, name **Contributor**, **Author**, **Editor** or **Admin**. Give the teammate’s email for a role change, enabling or disabling access, or a recovery email. If more than one membership matches, nothing changes.

An Editor invitation’s card reads **Invite [person@example.com](mailto:person@example.com) as Editor?**, using the address you gave, and offers **Send Editor invite**. A role-change card names the new role, such as **Change this member’s role to Editor?**, with **Change role to Editor**. Review the person and permission changes before approving.

The copilot cannot change the owner’s role or a Viewer’s role. For a Viewer, use **Change role** in your account’s **Team** tab.

| Request | Approval | Undo |
| --- | --- | --- |
| Disable a non-owner team member’s access | Yes | Available |
| Enable a disabled team member’s access | Yes | Available |
| Invite someone to your team | Yes | Available |
| List your team members | No | No |
| Resend an open team invitation | Yes | No |
| Revoke an open team invitation | Yes | No |

| Send a team member a recovery email | Yes | No | | Change a team member’s role | Yes | Available |

Role reductions and disabling try to update an open site too. Read the result: an undelivered reduction or disable is retried on the platform’s regular run while it still matches the member’s current state. A failed update can leave an open session usable. A failed attempt to turn access back on is not retried by this process.

**Site sign-in and Undo.** Disabling or enabling access also tries to update the member’s sign-in on the site. Read the result; a failed update can leave an open session usable or keep a re-enabled member unable to enter. If you disable yourself and the site is updated, you cannot press **Undo**; the owner or another Admin must restore access in **Team**. If a disable or role change ended access on managed client sites, **Undo** does not restore those sign-ins. After access is restored, the person opens the client site from their account again. See [client-site failure and retry limits](https://docs.amadalis.ai/agencies/agency-guide/#review-and-end-access).

## Visitor data

| Request | Approval | Undo |
| --- | --- | --- |
| Permanently erase one shopper account, separately from visitor data | Yes | No |

| Permanently erase one visitor’s captured data | Yes | No | | Permanently erase a selected set of visitors’ captured data | Yes | No | | Find a visitor by an allowed identifier | No | No | | Read your own marked test browser’s profile and recorded journey | No | No |

The copilot tells one browser’s story only for a test visitor you marked yourself in **Personalization**. A real visitor’s data is on [Visitor Data](https://docs.amadalis.ai/privacy/consent-and-visitor-data/#find-the-visitor-record).

Return to [the copilot request index](https://docs.amadalis.ai/reference/copilot/).

## Your next step

Choose a request that matches your task, then [ask the copilot](https://docs.amadalis.ai/copilot/copilot/). Review its proposed consequence before approving any change.