Sharing access with a teammate or VA

Postbean does not have member invitations yet. There is no screen where you invite someone to your workspace with their own login.

We would rather say that plainly than suggest a workaround that puts your accounts at risk.

Do not share your password

It is the obvious workaround and it is a bad one:

• Whoever has it can connect and disconnect social accounts, publish, delete posts, change the plan and issue API keys.
• Every action is attributed to you, so if something goes out that should not have, there is no way to tell who did it.
• If they sign in from another country, you both get security friction from the social networks.
• Changing your mind means changing the password and re-authenticating everywhere.

If you have already shared it, change it in Settings → Password and check Settings → Developers for API keys you did not create.

What works today

Give them their own Postbean account and connect the accounts there. If the VA is the one who manages the social accounts day to day, they can hold the connections and you keep yours separate. Each account has its own plan.

Use an API key for automation. If what you actually need is a tool or a script that drafts and schedules on your behalf, a scoped API key is the right shape: you choose exactly what it can do, and a key that writes drafts but cannot publish or delete is a real safety net. Revoking it is one click. See Connect your AI agent with MCP.

Use Approvals. The Publish → Approvals tab is there for content that should be reviewed before it goes out.

What is coming

Workspaces and organizations already exist underneath — a workspace has an owner and a member list, and posts, media and connections all belong to the workspace rather than to you personally. What is missing is the invitation flow on top. If team access is blocking you, tell us at support@postbean.app; it helps us prioritise.