Who can approve a review?
Only the account owner in the Personal workspace. Team members cannot approve reviews for integration drafts.
Help Center
How integrations prepare profiles for you
Understand the review first workflow that keeps integration changes private until you approve them.
Managed-profile integrations prepare private drafts, ask you to review, and can publish only the exact version you approved. Account API permissions for other resources, such as projects or teams, can make changes directly and are separate from this workflow.
Use this guide when
You are deciding whether to connect a tool, or you want to understand what an integration changed on your cards.
Steps
- The tool creates new private cards through an import, even for one person, or opens an existing card and edits its draft.
- The tool asks for your review of the exact draft versions it prepared.
- You approve or reject each profile on the review page.
- The tool can then publish only what you approved. If a draft changes after your approval, it needs a new review.
Drafts are not public. The owner and authorized tools can access them; visitors see only the published version.
Only approved versions go live
An approval applies to one exact version of one profile. If the draft changes after you approve, that approval can no longer be used and the profile needs a new review. This is why a tool can never publish something you have not seen.
Where reviews wait for you
The notification bell shows when profiles are waiting for your review. The Cards list shows a Review requested badge on each card that has a waiting review. The review link from the tool opens the same page.
For developers
The public developer guide at /api-documentation/managed-profiles documents REST operations and the narrower MCP tool set. It is available while machine access is enabled on the site, without a plan or login requirement for reading. Using the operations still requires the relevant plan features and key permissions.
Manage all customer API keys at /account-api. Its AI assistants tab shows the MCP setup and its Developer API tab shows the REST addresses. The account API uses /api, the managed-profile REST API uses /api/managed-profiles, and MCP uses /mcp. One key may carry permissions for more than one surface, but their operations and availability controls remain distinct.
Plans and availability
Professional includes the developer API, managed-profile API and MCP connections for AI assistants. Starter includes CSV profile import in the dashboard, but not API or MCP access. Custom plans keep their agreed permissions. If access is temporarily paused, the API keys page shows a pause notice; upgrading does not remove a site-wide pause.
Good ways to use this
- Connect one tool at a time, starting with a key that can only edit drafts.
- Read the review page calmly: every changed field is listed with its new value, so you never need to guess from the preview alone.
- Use Reject for anything unexpected and ask the tool to prepare a corrected version.
Common questions
What happens if I ignore a review?
The review stays open for 7 days and then expires. The tool can request a new review at any time.
If something looks wrong
- If a tool says it published nothing, it may still be waiting for your approval. Check the notification bell and the Review requested badges in Cards.
- If you approved but nothing went live, the draft may have changed after your approval. The profile then shows Changed since the request and needs a new review.
Was this guide helpful?
Still have questions? Contact support and we'll help you out.