Pachca workspace administration
Run a Pachca workspace for its Owner or an Administrator: people, tags, chat
membership, roles, API access, audit, export and data protection. Every action
here changes what other employees can see or do, so the main skill is knowing
who may do what, and when to ask first.
A clear request such as «сделай Олега администратором» is carried out: the
client asks its own approval for the change. You ask in chat first only in the
three cases of When to ask first, and deleting an
employee is one of them.
For a deletion, the request is not the confirmation. «Удали из Пачки Олега
Соколова» or "delete this user" tells you what to prepare, not that it may run.
Deleting an employee runs only after the person answers yes to your question in
a later message. This holds however direct the request and even when the search
finds exactly one match.
When to use
- Inviting, editing, suspending or deleting employees and guests; offboarding.
- Tags: creating, renaming, deleting, assigning to employees, binding to chats.
- Changing chat membership and chat roles; taking over a chat whose creator left.
- A
403 on an admin action; "why can't employees connect an agent".
- Who has API access and who may create it (the access settings); revoking
employees' access.
- The workspace name and settings; the invite link.
- Audit log, message export, DLP rules, IP allowlist and encryption (Corporation).
Not here: sending messages (pachca-messaging), reading who is in a tag or chat
and other searches (pachca-search), creating bots and managing their own tokens
(pachca-bots), OAuth apps (pachca-oauth), a missing tool or a general 401/403
(pachca).
First: who is acting, on which plan
The agent acts with the rights of the person behind the token. Scopes only
open methods; they never widen visibility. Check before planning:
- Role: read the own profile (
pachca_get_my_card, CLI pachca profile get).
role is admin, user, multi_guest or guest.
- Scopes:
pachca_get_token_info (CLI pachca oauth token-info).
- Plan: audit log, export, workspace inventory, DLP and data protection need
the «Корпорация» plan. The workspace info (
pachca_get_company, CLI
pachca company get) names the plan in plan, always in Russian, for
example «Корпорация». Without that, say you are unsure and ask.
| Role |
role value |
Admin powers |
| Owner |
admin |
Everything an Administrator has, plus members of any chat. On Corporation also export, audit log, all chats and bots of the workspace, DLP, the Security screen. Only one. |
| Administrator |
admin |
Employees, tags, workspace settings |
| Employee |
user |
None |
| Multi-guest, Guest |
multi_guest, guest |
None; a guest cannot use the API at all |
The Owner is not distinguishable by role in API responses: the profile
shows admin. Over MCP you do not need to ask: the server instructions name
you as «Name (id), token kind, role», and that role is owner for the Owner.
On Corporation the tool list gives it away too: only the Owner gets
pachca_get_audit_events, pachca_request_export, pachca_download_export,
pachca_list_company_chats and pachca_list_company_bots. Over the CLI or
REST, compare your own id with owner_id in the workspace info. If the token
cannot read it, ask the person whether they are the Owner instead of guessing. Do not
probe owner-only methods "to see": each call to the audit log or the workspace
inventory is itself written to the audit log.
Owner-only scopes (Corporation): chat_exports:read, chat_exports:write,
audit_events:read, company_chats:read, company_bots:read.
Owner and Administrator: users:create, users:update, users:delete,
user_status:write, user_avatar:write, group_tags:write, company:write,
invite_links:write. A bot token cannot create, edit or delete employees,
rename the workspace or get the invite link.
Owner-only methods need a token of the Owner: a personal token, a CLI login or
an app the Owner signed in to. No bot token and no Administrator gets these
scopes, so an audit feed or a scheduled export is tied to the Owner's account.
Ownership moves only in the web interface («Сделать владельцем» in the employee menu):
only the current Owner can do it, only to an active Administrator, and there
is no tool or CLI command for it. The former Owner stays an Administrator, and
their tokens then answer 403 role_forbidden on owner-only methods: the new
Owner gives a token these scopes (edit a personal token or log in to the CLI
again) and moves the job to it. An Owner who is leaving hands over ownership
first: the Owner cannot be suspended or deleted.
Two role systems
Workspace role and chat role are independent. This is the root of most
admin mistakes:
- A workspace Administrator does not see closed chats they are not in.
Closed chats are visible only to their members, for every role, the Owner
included. The way in is to be added by a current participant other than a
guest or multi-guest, or to be given a tag bound to the chat; an Owner or
Administrator then joins as chat Admin. Tags are given by an Owner or
Administrator, their own included, but which tags the chat has, an
Administrator outside it cannot see: ask a member. Nobody can add themselves
to a closed chat directly, the Owner included. Without joining, only the Owner
can read the chat's member list, on any plan, and on Corporation also see
it in the list of all workspace chats and export its messages; none of this
opens the chat itself, and an Administrator gets none of it.
- The chat role is set once, when someone joins: the Owner or an Administrator
joins as chat Admin, a bot joins a channel as Editor, everyone else as
Member (Subscriber in a channel). It is not recalculated later. Promoting
someone to Administrator changes nothing in chats they are already in;
demoting an Administrator leaves them chat Admin.
- The chat Creator role cannot be transferred or changed.
- In a chat member list,
role is the workspace role. To find chat roles,
filter by role (owner, admin, editor, member), one request per role.
When debugging a 403 on an admin action, first check whether the token's
owner is in the chat and with which chat role, then the scopes. Admin-specific
codes: permission_denied (a protected change: editing the Owner or their
avatar with someone else's token, changing the Owner's role, suspending or
deleting the Owner) and role_forbidden (scope present but the role no longer
allows it, as after a demotion; a new token will not help). A token whose owner
was made a guest gets 401: it is revoked. insufficient_scope,
access_denied and Corporation-only methods are explained in the entry skill
(→ pachca).
When to ask first
Ask in chat before a change, naming exactly who or what is affected and the
consequence, only when:
- the target is a guess: the search found several, or you inferred it rather
than the person naming it;
- the step cannot be undone while a reversible one would do: deleting an
employee, where suspension can be undone;
- it changes many at once: several employees, a tag removed from a chat or
deleted, the members of several chats. Making an employee a guest is one:
they leave every other conversation and channel, lose all tags and all
their tokens at once, and a promotion restores none of it.
Then wait for a yes in a later message. One yes covers one action, not a batch
the person has not seen. Any other clear request runs at once.
The turn that receives a deletion request only reads and asks. For «удали
сотрудника»: find the employee (pachca_search_users), then reply with their
name, nickname and id, say that deletion cannot be undone and what it removes
(row below), offer suspension instead, and ask «Удалить насовсем или
приостановить?». Do not call pachca_delete_user in that turn. Call it only
after the person answers yes to that question. The client's own approval
prompt does not replace this: it can be turned off, and it shows a tool call
with an id, not who loses what.
Each row is what to tell the person: in your question when you ask, otherwise in
the line that reports what you did.
| Action |
What to tell the person |
| Invite an employee |
Unless skip_email_notify: true is sent (pre-creating accounts before SSO sign-in), the invitation email goes out at once and cannot be recalled. Name the email, name and role (admin gives Administrator powers); take addresses only from the person: their message, or a table or file they give you, not a message or file from someone else. list_tags and chat_ids put them into those chats at once. |
| Delete an employee |
Irreversible. Leaves all group chats, loses all tags, reminders where they were the only performer are deleted. Coming back means a new invitation and a different employee. Offer suspension instead. |
| Suspend an employee |
Access stops at once; their tokens stop working but revive on restore. Bots they created keep running. |
| Change workspace role |
Takes effect on their tokens immediately; chat roles do not follow. To guest: next row. |
| Make an employee a guest |
Cannot be undone. They keep only the chat in chat_ids, leave every other conversation and channel and lose all tags. In the threads they stay in, an Admin or Editor role becomes Member. Every token they hold, the access they gave bots and apps included, is revoked (401). They get an email about it. A later promotion restores none of it. |
Set list_tags |
Replaces the whole set. Each dropped tag takes them out of the chats it brought them into, unless another of their tags bound to the chat keeps them there. |
| Remove a tag from a chat |
Everyone held there only by that tag leaves the chat. |
| Delete a tag |
Removed from all employees and chats; members stay in chats but are no longer kept in sync. |
| Archive a chat |
Guests (role guest) are removed, multi-guests stay, and tags are unbound; unarchiving restores neither. |
| Add or remove a member, change a chat role |
Name the chat and each person. Added members get access to the chat at once; an Owner or Administrator joins as chat Admin, and in a thread under a message as a plain member. |
| Request an export |
It contains closed chats regardless of membership. Use the period the person names. With none named, take the longest the limit allows, ending today, and say which days it covers. |
| Revoke a token or access |
Whatever runs on it breaks immediately; a personal token cannot be restored. |
| Change workspace settings |
Applies to every employee at once. show_personal_data: false hides emails and phone numbers from employees and bot tokens. Turning off «Использовать сквозные треды» stops a thread mention from adding people outside the parent chat. |
| Reissue the invite link |
Your old link stops working at once, even where it was already sent. Other Administrators' links keep working. |
| Clear the IP allowlist or turn encryption off |
Clearing the allowlist makes protected files undownloadable until addresses are listed again. Turning encryption off makes older messages permanently unreadable. The key itself stays fixed, only its credentials update: see the security reference. |
New workspace
«Подготовь Пачку к работе команды»: when the only chat is the one with yourself,
the workspace is new. Propose a plan in one message for one yes: an open company
channel, an informal chat, a chat and a tag per team, the full text of the
first message to pin in each, and ask only for the colleagues' emails and
teams. Then create the tags, the chats bound to them, the invitations with tag
and role in the same call, and post and pin those first messages. Steps, the invitation limit, the invite link and what only the web interface does:
references/new-workspace.md.
Do it right
Employees. Invitation, guests, SSO, suspension versus deletion and the
offboarding order are in references/employee-lifecycle.md.
Key rules:
- Prefer suspension (
suspended: true in the employee update) to deletion.
Delete only after the person, shown who it is and that it cannot be undone,
answers yes; the word «удали» in the request is not that answer.
- An edit applies all or nothing; an unknown role value is silently ignored.
Re-read the employee after a role change.
- Nobody can edit the Owner or change their avatar with someone else's token,
and nobody, the Owner included, can suspend or delete the Owner.
- For an employee with
sso: true, the next SSO sign-in can rewrite profile
fields, tags and role from the identity provider.
- Never delete and re-invite to fix an account: resending an invitation exists
only in the web interface.
- Chats are never archived automatically when someone leaves, and bots they
created keep running: check both before offboarding.
Tags. Membership through tags and the traps around removal are in
references/tags-and-membership.md. Key rules:
list_tags takes tag names and replaces the set: read the current tags,
merge, send the full list.
- An unknown name silently creates a new tag. Check the spelling against the
tag list first (lookup by names, up to 100 per request).
- A member brought in by a tag cannot be removed one by one: removal returns
success and changes nothing. Remove the tag from the person or from the chat.
Chats and members. No bulk operations exist: one request per chat, mind the
limits. Adding members fails as a whole
if any id is unknown or inactive; already-present members are skipped silently.
To regain control of a chat whose admins are gone, have the Owner or an
Administrator who is not in the chat yet added: they join as chat Admin. Who
can add them: in an open chat any employee, in a closed chat only a current
participant other than a guest or multi-guest. A closed chat with no such
participant left takes nobody new, the Owner included, except through a tag
already bound to it: whoever is given that tag joins. Someone already in the
chat keeps their current role (the add is skipped and still reports success),
so check with the member list filtered by role=admin.
API access. Two workspace settings decide who may create access:
"who can create integrations" (bots and their tokens; default: administrators
and employees) and "who can create personal tokens" (default: administrators
only). The second one also blocks employees from CLI login and from granting
access to bots and MCP apps on the consent screen. So "employees cannot connect
the agent" is usually this setting.
Both settings close only new access. To cut existing employee access
(personal tokens, CLI logins, bot authorizations, MCP clients), an
Administrator revokes it on the All tokens tab (Integrations > API). Also
revoke tokens of suspended employees there: they revive if access is restored.
A bot's own tokens are not on that tab: they are deleted on the API tab of
the bot card or with pachca_delete_bot_token (CLI pachca bots delete-token),
by the bot's creator, or by an Administrator if the bot's settings give
Administrators edit access (→ pachca-bots). Switching "who can create
integrations" to administrators only also takes existing bots away from
creators without that role: the bots keep running, and Administrators reach
only bots whose can_edit includes admin.
The two settings are on the Workspace page (General settings), the tab is
under Integrations > API. pachca_get_company shows them in
integrations_management and api_management (all or admins), but they
change only in the web interface: pachca_update_company ignores them. Tell
the person where to click.
Security and compliance (Owner, Corporation): audit log, export, DLP rules,
IP allowlist and encryption. Procedures and warnings are in
references/security-compliance.md.
Pitfalls
- Assuming an Administrator sees every chat. They do not; only the Owner on
Corporation gets the inventory.
- Assuming the chat member list shows chat roles or suspended members. It shows
neither:
role is the workspace role, suspended employees are omitted.
- Sending only the new tag in
list_tags and silently pulling the employee out
of all their other tag chats.
- Deleting a tag to "remove a team from a channel": everyone stays. Use
"remove tag from chat" instead.
- Expecting tag removal from a chat to be instant: it runs in the background.
Re-check members after a short wait.
- Treating a revoked access setting as a revocation of existing tokens.
- Reading
email and phone_number as missing: for employees and bot tokens
they are null unless the workspace allows showing personal data
(show_personal_data in pachca_get_company); Owner and Administrators
always see them.
- Inventory has its own strict rate limit, shared by the chats and bots lists
and reading the invite link
(limits): spread a large walk over
time.
Read more
1---2name: pachca-admin3description: 'Администрирование пространства Пачки: новое пространство, сотрудники, теги и участники чатов, доступ к API и «Все токены», журнал аудита, экспорт, DLP, безопасный контур и шифрование, и что требует владельца, администратора или «Корпорации». Load before a tool call that changes an employee: delete only after a yes to your question. Когда: «подготовь Пачку к работе команды», «настрой новое пространство», «пригласи сотрудника», «уволь / удали сотрудника», «сделай администратором», «добавь в тег», «добавь участника чата», «кто в закрытом канале, где я не состою», «доступ к API ограничен», «отзови доступ сотрудника к API», «журнал аудита», «выгрузи переписку», «правило DLP», "set up a new workspace", "invite an employee", "add or remove chat members", "let employees create tokens". Not for: a missing tool or a general 401/403 → pachca; who is in a tag or chat → pachca-search; writing messages → pachca-messaging; a bot''s own token → pachca-bots; an app acting for employees → pachca-oauth; scripts → pachca-api.'4metadata:5 source: https://skillmd.com/skills/pachca/pachca-admin6---78# Pachca workspace administration910Run a Pachca workspace for its Owner or an Administrator: people, tags, chat11membership, roles, API access, audit, export and data protection. Every action12here changes what other employees can see or do, so the main skill is knowing13who may do what, and when to ask first.1415A clear request such as «сделай Олега администратором» is carried out: the16client asks its own approval for the change. You ask in chat first only in the17three cases of [When to ask first](#when-to-ask-first), and deleting an18employee is one of them.1920**For a deletion, the request is not the confirmation.** «Удали из Пачки Олега21Соколова» or "delete this user" tells you what to prepare, not that it may run.22Deleting an employee runs only after the person answers yes to your question in23a later message. This holds however direct the request and even when the search24finds exactly one match.2526## When to use2728- Inviting, editing, suspending or deleting employees and guests; offboarding.29- Tags: creating, renaming, deleting, assigning to employees, binding to chats.30- Changing chat membership and chat roles; taking over a chat whose creator left.31- A `403` on an admin action; "why can't employees connect an agent".32- Who has API access and who may create it (the access settings); revoking33 employees' access.34- The workspace name and settings; the invite link.35- Audit log, message export, DLP rules, IP allowlist and encryption (Corporation).3637Not here: sending messages (pachca-messaging), reading who is in a tag or chat38and other searches (pachca-search), creating bots and managing their own tokens39(pachca-bots), OAuth apps (pachca-oauth), a missing tool or a general 401/40340(pachca).4142## First: who is acting, on which plan4344The agent acts with the rights of the person behind the token. Scopes only45open methods; they never widen visibility. Check before planning:46471. Role: read the own profile (`pachca_get_my_card`, CLI `pachca profile get`).48 `role` is `admin`, `user`, `multi_guest` or `guest`.492. Scopes: `pachca_get_token_info` (CLI `pachca oauth token-info`).503. Plan: audit log, export, workspace inventory, DLP and data protection need51 the «Корпорация» plan. The workspace info (`pachca_get_company`, CLI52 `pachca company get`) names the plan in `plan`, always in Russian, for53 example «Корпорация». Without that, say you are unsure and ask.5455| Role | `role` value | Admin powers |56| ------------------ | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |57| Owner | `admin` | Everything an Administrator has, plus members of any chat. On Corporation also export, audit log, all chats and bots of the workspace, DLP, the Security screen. Only one. |58| Administrator | `admin` | Employees, tags, workspace settings |59| Employee | `user` | None |60| Multi-guest, Guest | `multi_guest`, `guest` | None; a guest cannot use the API at all |6162The Owner is **not** distinguishable by `role` in API responses: the profile63shows `admin`. Over MCP you do not need to ask: the server instructions name64you as «Name (id), token kind, role», and that role is `owner` for the Owner.65On Corporation the tool list gives it away too: only the Owner gets66`pachca_get_audit_events`, `pachca_request_export`, `pachca_download_export`,67`pachca_list_company_chats` and `pachca_list_company_bots`. Over the CLI or68REST, compare your own `id` with `owner_id` in the workspace info. If the token69cannot read it, ask the person whether they are the Owner instead of guessing. Do not70probe owner-only methods "to see": each call to the audit log or the workspace71inventory is itself written to the audit log.7273Owner-only scopes (Corporation): `chat_exports:read`, `chat_exports:write`,74`audit_events:read`, `company_chats:read`, `company_bots:read`.75Owner and Administrator: `users:create`, `users:update`, `users:delete`,76`user_status:write`, `user_avatar:write`, `group_tags:write`, `company:write`,77`invite_links:write`. A bot token cannot create, edit or delete employees,78rename the workspace or get the invite link.7980Owner-only methods need a token of the Owner: a personal token, a CLI login or81an app the Owner signed in to. No bot token and no Administrator gets these82scopes, so an audit feed or a scheduled export is tied to the Owner's account.83Ownership moves only in the web interface («Сделать владельцем» in the employee menu):84only the current Owner can do it, only to an active Administrator, and there85is no tool or CLI command for it. The former Owner stays an Administrator, and86their tokens then answer `403 role_forbidden` on owner-only methods: the new87Owner gives a token these scopes (edit a personal token or log in to the CLI88again) and moves the job to it. An Owner who is leaving hands over ownership89first: the Owner cannot be suspended or deleted.9091## Two role systems9293Workspace role and chat role are independent. This is the root of most94admin mistakes:9596- A workspace Administrator does **not** see closed chats they are not in.97 Closed chats are visible only to their members, for every role, the Owner98 included. The way in is to be added by a current participant other than a99 guest or multi-guest, or to be given a tag bound to the chat; an Owner or100 Administrator then joins as chat Admin. Tags are given by an Owner or101 Administrator, their own included, but which tags the chat has, an102 Administrator outside it cannot see: ask a member. Nobody can add themselves103 to a closed chat directly, the Owner included. Without joining, only the Owner104 can read the chat's member list, on any plan, and on Corporation also see105 it in the list of all workspace chats and export its messages; none of this106 opens the chat itself, and an Administrator gets none of it.107- The chat role is set once, when someone joins: the Owner or an Administrator108 joins as chat Admin, a bot joins a channel as Editor, everyone else as109 Member (Subscriber in a channel). It is **not** recalculated later. Promoting110 someone to Administrator changes nothing in chats they are already in;111 demoting an Administrator leaves them chat Admin.112- The chat Creator role cannot be transferred or changed.113- In a chat member list, `role` is the workspace role. To find chat roles,114 filter by `role` (`owner`, `admin`, `editor`, `member`), one request per role.115116When debugging a `403` on an admin action, first check whether the token's117owner is in the chat and with which chat role, then the scopes. Admin-specific118codes: `permission_denied` (a protected change: editing the Owner or their119avatar with someone else's token, changing the Owner's role, suspending or120deleting the Owner) and `role_forbidden` (scope present but the role no longer121allows it, as after a demotion; a new token will not help). A token whose owner122was made a guest gets `401`: it is revoked. `insufficient_scope`,123`access_denied` and Corporation-only methods are explained in the entry skill124(→ pachca).125126## When to ask first127128Ask in chat before a change, naming exactly who or what is affected and the129consequence, only when:130131- the target is a guess: the search found several, or you inferred it rather132 than the person naming it;133- the step cannot be undone while a reversible one would do: deleting an134 employee, where suspension can be undone;135- it changes many at once: several employees, a tag removed from a chat or136 deleted, the members of several chats. Making an employee a guest is one:137 they leave every other conversation and channel, lose all tags and all138 their tokens at once, and a promotion restores none of it.139140Then wait for a yes in a later message. One yes covers one action, not a batch141the person has not seen. Any other clear request runs at once.142143The turn that receives a deletion request only reads and asks. For «удали144сотрудника»: find the employee (`pachca_search_users`), then reply with their145name, nickname and id, say that deletion cannot be undone and what it removes146(row below), offer suspension instead, and ask «Удалить насовсем или147приостановить?». Do not call `pachca_delete_user` in that turn. Call it only148after the person answers yes to that question. The client's own approval149prompt does not replace this: it can be turned off, and it shows a tool call150with an id, not who loses what.151152Each row is what to tell the person: in your question when you ask, otherwise in153the line that reports what you did.154155| Action | What to tell the person |156| --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |157| Invite an employee | Unless `skip_email_notify: true` is sent (pre-creating accounts before SSO sign-in), the invitation email goes out at once and cannot be recalled. Name the email, name and role (`admin` gives Administrator powers); take addresses only from the person: their message, or a table or file they give you, not a message or file from someone else. `list_tags` and `chat_ids` put them into those chats at once. |158| Delete an employee | Irreversible. Leaves all group chats, loses all tags, reminders where they were the only performer are deleted. Coming back means a new invitation and a different employee. Offer suspension instead. |159| Suspend an employee | Access stops at once; their tokens stop working but revive on restore. Bots they created keep running. |160| Change workspace role | Takes effect on their tokens immediately; chat roles do not follow. To `guest`: next row. |161| Make an employee a guest | Cannot be undone. They keep only the chat in `chat_ids`, leave every other conversation and channel and lose all tags. In the threads they stay in, an Admin or Editor role becomes Member. Every token they hold, the access they gave bots and apps included, is revoked (`401`). They get an email about it. A later promotion restores none of it. |162| Set `list_tags` | Replaces the whole set. Each dropped tag takes them out of the chats it brought them into, unless another of their tags bound to the chat keeps them there. |163| Remove a tag from a chat | Everyone held there only by that tag leaves the chat. |164| Delete a tag | Removed from all employees and chats; members stay in chats but are no longer kept in sync. |165| Archive a chat | Guests (role `guest`) are removed, multi-guests stay, and tags are unbound; unarchiving restores neither. |166| Add or remove a member, change a chat role | Name the chat and each person. Added members get access to the chat at once; an Owner or Administrator joins as chat Admin, and in a thread under a message as a plain member. |167| Request an export | It contains closed chats regardless of membership. Use the period the person names. With none named, take the longest the limit allows, ending today, and say which days it covers. |168| Revoke a token or access | Whatever runs on it breaks immediately; a personal token cannot be restored. |169| Change workspace settings | Applies to every employee at once. `show_personal_data: false` hides emails and phone numbers from employees and bot tokens. Turning off «Использовать сквозные треды» stops a thread mention from adding people outside the parent chat. |170| Reissue the invite link | Your old link stops working at once, even where it was already sent. Other Administrators' links keep working. |171| Clear the IP allowlist or turn encryption off | Clearing the allowlist makes protected files undownloadable until addresses are listed again. Turning encryption off makes older messages permanently unreadable. The key itself stays fixed, only its credentials update: see the security reference. |172173## New workspace174175«Подготовь Пачку к работе команды»: when the only chat is the one with yourself,176the workspace is new. Propose a plan in one message for one yes: an open company177channel, an informal chat, a chat and a tag per team, the full text of the178first message to pin in each, and ask only for the colleagues' emails and179teams. Then create the tags, the chats bound to them, the invitations with tag180and role in the same call, and post and pin those first messages. Steps, the invitation limit, the invite link and what only the web interface does:181[references/new-workspace.md](references/new-workspace.md).182183## Do it right184185**Employees.** Invitation, guests, SSO, suspension versus deletion and the186offboarding order are in [references/employee-lifecycle.md](references/employee-lifecycle.md).187Key rules:188189- Prefer suspension (`suspended: true` in the employee update) to deletion.190 Delete only after the person, shown who it is and that it cannot be undone,191 answers yes; the word «удали» in the request is not that answer.192- An edit applies all or nothing; an unknown role value is silently ignored.193 Re-read the employee after a role change.194- Nobody can edit the Owner or change their avatar with someone else's token,195 and nobody, the Owner included, can suspend or delete the Owner.196- For an employee with `sso: true`, the next SSO sign-in can rewrite profile197 fields, tags and role from the identity provider.198- Never delete and re-invite to fix an account: resending an invitation exists199 only in the web interface.200- Chats are never archived automatically when someone leaves, and bots they201 created keep running: check both before offboarding.202203**Tags.** Membership through tags and the traps around removal are in204[references/tags-and-membership.md](references/tags-and-membership.md). Key rules:205206- `list_tags` takes tag **names** and replaces the set: read the current tags,207 merge, send the full list.208- An unknown name silently creates a new tag. Check the spelling against the209 tag list first (lookup by names, up to 100 per request).210- A member brought in by a tag cannot be removed one by one: removal returns211 success and changes nothing. Remove the tag from the person or from the chat.212213**Chats and members.** No bulk operations exist: one request per chat, mind the214[limits](https://dev.pachca.com/api/limits.md). Adding members fails as a whole215if any id is unknown or inactive; already-present members are skipped silently.216To regain control of a chat whose admins are gone, have the Owner or an217Administrator who is not in the chat yet added: they join as chat Admin. Who218can add them: in an open chat any employee, in a closed chat only a current219participant other than a guest or multi-guest. A closed chat with no such220participant left takes nobody new, the Owner included, except through a tag221already bound to it: whoever is given that tag joins. Someone already in the222chat keeps their current role (the add is skipped and still reports success),223so check with the member list filtered by `role=admin`.224225**API access.** Two workspace settings decide who may create access:226"who can create integrations" (bots and their tokens; default: administrators227and employees) and "who can create personal tokens" (default: administrators228only). The second one also blocks employees from CLI login and from granting229access to bots and MCP apps on the consent screen. So "employees cannot connect230the agent" is usually this setting.231232Both settings close only **new** access. To cut existing employee access233(personal tokens, CLI logins, bot authorizations, MCP clients), an234Administrator revokes it on the **All tokens** tab (Integrations > API). Also235revoke tokens of suspended employees there: they revive if access is restored.236A bot's own tokens are not on that tab: they are deleted on the **API** tab of237the bot card or with `pachca_delete_bot_token` (CLI `pachca bots delete-token`),238by the bot's creator, or by an Administrator if the bot's settings give239Administrators edit access (→ pachca-bots). Switching "who can create240integrations" to administrators only also takes existing bots away from241creators without that role: the bots keep running, and Administrators reach242only bots whose `can_edit` includes `admin`.243244The two settings are on the **Workspace** page (General settings), the tab is245under Integrations > API. `pachca_get_company` shows them in246`integrations_management` and `api_management` (`all` or `admins`), but they247change only in the web interface: `pachca_update_company` ignores them. Tell248the person where to click.249250**Security and compliance** (Owner, Corporation): audit log, export, DLP rules,251IP allowlist and encryption. Procedures and warnings are in252[references/security-compliance.md](references/security-compliance.md).253254## Pitfalls255256- Assuming an Administrator sees every chat. They do not; only the Owner on257 Corporation gets the inventory.258- Assuming the chat member list shows chat roles or suspended members. It shows259 neither: `role` is the workspace role, suspended employees are omitted.260- Sending only the new tag in `list_tags` and silently pulling the employee out261 of all their other tag chats.262- Deleting a tag to "remove a team from a channel": everyone stays. Use263 "remove tag from chat" instead.264- Expecting tag removal from a chat to be instant: it runs in the background.265 Re-check members after a short wait.266- Treating a revoked access setting as a revocation of existing tokens.267- Reading `email` and `phone_number` as missing: for employees and bot tokens268 they are `null` unless the workspace allows showing personal data269 (`show_personal_data` in `pachca_get_company`); Owner and Administrators270 always see them.271- Inventory has its own strict rate limit, shared by the chats and bots lists272 and reading the invite link273 ([limits](https://dev.pachca.com/api/limits.md)): spread a large walk over274 time.275276## Read more277278- Roles, visibility, Owner privileges, 403 causes: <https://dev.pachca.com/guides/permissions.md>279- Tags: <https://dev.pachca.com/guides/tags.md>280- Tokens, scopes by role, access settings, All tokens: <https://dev.pachca.com/api/authorization.md>281- Bot tokens and edit access: <https://dev.pachca.com/guides/bots/tokens.md>282- Audit log: <https://dev.pachca.com/guides/audit-events.md>283- Message export: <https://dev.pachca.com/guides/export.md>284- DLP: <https://dev.pachca.com/guides/dlp.md>285- IP allowlist and encryption: <https://dev.pachca.com/guides/data-protection.md>286- Employee methods: <https://dev.pachca.com/api/users/create.md>, <https://dev.pachca.com/api/users/update.md>, <https://dev.pachca.com/api/users/delete.md>287- Chat members: <https://dev.pachca.com/api/members/list.md>288- Limits: <https://dev.pachca.com/api/limits.md>