Permissions and reviewed changes

Understand what each authorization allows.

Owner and reader access

| Access level | What it allows | | --- | --- | | Read (owner:read) | Search and inspect your authorized directory. No edits. | | Propose changes (owner:propose) | Prepare listing edits and screenshot covers for owner review. Live content stays unchanged. | | Approve in conversation (owner:approve) | Record your approval of an exact change set after you confirm its changes in the conversation. Administrator authority is required. Does not publish. | | Publish reviewed changes (owner:publish) | Publish only an exact change set you approved, in DirectoryHub or in conversation. A changed listing needs fresh approval. | | Private draft editing (owner:apply_draft) | Admin-only, opt-in and unticked by default. Edits stay in private drafts. Publishing requires the separate owner:publish permission or the owner in DirectoryHub. | | Paid enrichment (owner:enrich) | Admin-only, opt-in and unticked by default. Before selecting it, set a positive whole-number credit cap for this connection; there is no default amount. Each paid run shows its credit cost in the conversation before it starts. Runs above the remaining cap are refused. Admins can raise or lower the cap in AI connections; a cap of 0 stops new runs. Capturing screenshots with your client's own tools does not use DirectoryHub enrichment credits. | | Reader (reader:read) | Read only the published fields shared by the owner. No private records or workspace management. | | Stay signed in (offline_access) | Renew the existing connection with refresh access. Does not expand scopes. |

Start with Read and add only the capabilities you need. Draft edits, paid runs, approval and publishing are separate admin-only permissions. Editors and members cannot grant them. An assistant cannot grant itself permissions or change its credit cap. Current workspace authority, directory access and feature availability are checked on requests.

Review before changes

Start with a search. For management, ask for a proposed improvement and review the changes in DirectoryHub. A proposal does not publish a listing. Connecting a client does not grant payment, publication or enrichment permissions.

Do not request broader scopes just to resolve a connection error. Paid enrichment, applying changes and publication have their own permissions and review requirements.

Add permissions to an existing connector

A client keeps the scopes it registered with. To add a new permission, delete the connector in ChatGPT, Claude or your other AI client, then add it again and authorize the permissions you want. Reconnecting alone does not update its registered scopes. Existing connections do not gain permissions automatically.

Disconnect

Revoke the specific authorization from AI connections. Reconnecting requires a new authorization. Revocation does not erase data already returned to the client.