> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apostra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Invite and manage a client's access

> Invite a client to one of your advertisers, approve or suspend them, and change their role in Advertiser settings

You give a person at a client company access to one advertiser in your Seller
Account, and manage that access afterward, in **Client access** on the
advertiser's **Advertiser settings**. The page makes the change. An agent does
not: `save_advertiser_access` is a page-only tool, so it does not appear in an
agent's tool list, the public V3 HTTP API or the SDKs. An agent can still read
the advertiser with
[`get` and `kind: "advertiser_access"`](https://docs.apostra.com/v2/buyer/advertisers/tasks/read-advertiser-client-access)
to see who has access and what the page offers, and then send the person to the
page to make the change.

> [!NOTE]
>
> Only an organization administrator signed in directly can make these
> changes. API keys, service tokens, agents acting for someone else, and
> impersonated or parent-account sessions are refused. Client access must also
> be turned on for your account.

## In the app

Open **Advertiser settings** from the pencil beside the advertiser in the left
rail. **Invite someone from the client** takes their work email, their
company's website domain, and what they can do (**Can view**, **Can edit**, or
**Admin**). Each person then shows only the buttons that apply to them right
now: **Approve**, **Suspend**, **Reactivate**, **Revoke access**, and **Change
role**. If Apostra refuses a change, the section shows the reason it gave.

There are no REST routes for these changes. The advertiser roster that shows
each client's state is a read; see
[List organization advertisers](https://docs.apostra.com/v2/buyer/advertisers/tasks/list-organization-advertisers.md).

## Invite a client

Apostra emails the person a one-time link. They sign in with that exact email
address and accept. Accepting does not give them access: you still approve
them. The page tells you whether the email was `sent` or `failed`. If it
failed, `invite.available` on the read stays `true` while the same invitation
can be sent again. Sending the same invitation again does not create a second
one.

## Approve, suspend, reactivate, or revoke

Approve works once the person has accepted the invitation. Suspend and revoke
take effect immediately. They stop the person's access without erasing the
advertiser's campaigns or history.

## Change a role

You can change the role of an approved person who has accepted. The roles are
fixed bundles: a viewer reads, an editor reads and writes, and an
administrator can also administer the advertiser. None of them includes
billing or payment.

## End older self-serve access

An older self-serve access record appears on the advertiser's **Client
access** with **Revoke access** when the read shows `canRevoke: true`. A
lifecycle that belongs to another advertiser, is already revoked, or is on a
System advertiser is refused.

## When a change is refused

| Refusal | What to do |
| - | - |
| Not an administrator signed in directly | Ask an organization administrator to make the change. |
| Client access is not enabled for the account | Contact Apostra. |
| The action is not offered | Reload the advertiser; the page offers only what the server allows. |
| The revision is out of date | Someone changed this client since you loaded it. Reload and retry. |
| The advertiser is a System advertiser | Apostra operates it. Its access cannot be changed. |
| The client does not belong to that advertiser | Open the settings of the advertiser the client belongs to. |

If a result is lost, reload the advertiser before retrying. A change that
already went through never repeats, and the page shows the result.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.