Account & billing

Team and roles

Invite teammates to your workspace and choose what each can do: who can add prompts and spend credits, who can connect data sources, and who can only view.

Open in ChatGPT Open in Claude

An AmICited workspace is shared. Everyone you invite sees the same domains, prompts and reports, and every run is paid from the same credit balance. A role decides what each person can change. Because AmICited is part of FlowHunt, workspace membership and roles are managed in FlowHunt’s workspace settings and apply across both.

The roles at a glance#

Role	In one line
Owner	Owns the workspace and its billing. Exactly one per workspace.
Admin	Full control, including members, data source connections and credit settings.
Editor	Runs the tracking day to day: domains, prompts, competitors, tags, articles and audits.
Member	Read-only. Sees every dashboard and report, changes nothing.
Guest	No access to AmICited data. Used for client access in other FlowHunt products.
Maintainer	No access to AmICited domains, prompts or metrics. Built for integration upkeep in FlowHunt.

What each role can do in AmICited#

Action	Owner	Admin	Editor	Member
View dashboard, prompts, sources, competitors and reports	Yes	Yes	Yes	Yes
Add, edit and delete domains, prompts, competitors and tags	Yes	Yes	Yes	No
Run Process now, generate articles, build semantic maps, run audits	Yes	Yes	Yes	No
Manage annotations, uptime monitors, backlinks and link building rules	Yes	Yes	Yes	No
View connected data sources	Yes	Yes	Yes	Yes
Connect, remap or disconnect data sources (Search Console, ads, stores)	Yes	Yes	No	No
See which AI agents are connected via MCP	Yes	Yes	Yes	Yes
Revoke an AI agent’s MCP connection	Yes	Yes	Yes	No
Create API keys	Yes	Yes	Yes	No
View the member list	Yes	Yes	Yes	Yes
Add, change or remove members	Yes	Yes	No	No
Change credit alerts, limits and auto-recharge	Yes	Yes	No	No
Transfer ownership, delete the workspace	Yes	No	No	No

Guest and Maintainer are not granted access to AmICited domains, prompts or metrics, so they cannot use the dashboard. Maintainer keeps read access to a few technical areas, such as data source connections and some audit results, for integration upkeep.

Anything that spends credits needs Editor or above

Adding prompts, re-running them, generating articles and running audits all spend credits. Give the Member role to stakeholders who should see results without being able to change what is tracked or what it costs.

Invite a teammate#

Open the workspace users
Go to Workspace Settings → Users. You need to be the Owner or an Admin to add people.
Add the member
Click Add Member, enter their User Email and pick a User role. You cannot add yourself, and you cannot add someone as Owner.
They accept the invitation
They receive an invitation email to the workspace. Once they sign in, they see every AmICited domain in it, subject to their role.

To change a role, open the member and use Update Member. To remove someone, use Remove Member. The Owner’s role cannot be changed this way.

The Owner and billing#

Each workspace has exactly one Owner. The workspace runs on the Owner’s subscription and credits: plan limits (domains, prompts, engines) come from the Owner’s plan, and every AI response is charged to the Owner’s balance.

To hand a workspace over, the Owner uses Transfer Ownership on another member. The new Owner gets full control, including deleting the workspace or removing members, and from then on the new Owner’s credits are used for the workspace. The previous Owner becomes an Admin.

AI agents and the API use your role#

An AI agent connected through the MCP server acts as the person who connected it. It can only do what that person’s role allows: an agent connected by a Member can read reports but cannot add prompts, even if the agent was granted write access on the consent screen. OAuth access is also limited to the workspace chosen when connecting.

This makes the role the safety boundary for automation. If a teammate wants an agent to only brief them on results, the Member role is enough.

Recommended setups#

In-house team. One Owner (usually whoever holds the budget), one or two Admins, Editors for the people who manage prompts and content, Members for leadership and sales.
Agency. Keep the Owner and Admin roles in the agency. Give client stakeholders Member access so they can see their dashboards without changing tracking or spending credits.
Least privilege for integrations. Only Owners and Admins can connect Search Console, ad accounts or stores. Keep that list short, because connections pull data from accounts outside AmICited.

Plans and limits What the Owner’s plan includes. Credits Alerts, limits and auto-recharge for the shared balance. Connect the MCP server Connect an AI agent to your workspace. Search Console and Bing Data sources that Owners and Admins connect.