Inviting and removing members

Owners and admins manage people on the Members page. It lists everyone in the organization with their name, email and role, then the invitations still pending. Members see the same list without the controls.

Invitations

Owners and admins invite people from Invite a teammate on the Members page, with a role. A pending invitation shows as Invited, with Copy link and Cancel. Only an owner can invite someone as an owner. The steps for both sides are in Invite your team.

Change a role

1. Open the Members page.
2. In the person’s row, open the role menu and pick member, admin or owner.

The change applies at once. See Roles for what each role may do.

• Admins can switch people between member and admin.
• Only an owner can make someone an owner, or change an owner’s role.
• The last owner always stays an owner.
• Nobody changes their own role. Your row shows your role without a menu.

Hand the organization over

There is no separate transfer step. Ownership moves through roles:

1. As an owner, set the new person’s role to owner.
2. Ask them to change your role to admin or member, or to remove you.

An organization can have several owners, so you can also stop after the first step.

Remove a member

1. Open the Members page.
2. Press Remove in the person’s row.

There is no confirmation step. The person loses access to the organization straight away. Their Super Flows account stays, and so do any other organizations they belong to. If you remove someone by mistake, invite them again.

Only an owner can remove an owner, and the last owner can’t be removed. Nobody removes themselves on the Members page, and there is no button to leave an organization. To leave, ask one of its owners or admins to remove you.

What happens to a removed member’s work

Most of what a member makes belongs to the organization, so it stays where it is.

Their	After removal
Projects, workflows, agents and databases	Stay, unchanged.
Skills owned by the organization	Stay, unchanged.
Runs they started, versions they published	Stay in each workflow’s history, credited to “Former member”.
Conversations with the organization’s agents	Stay on each agent’s Chat tab.
App connections they made	Stay, and keep acting as the account they connected.
API keys they created	Stay, and keep working. Keys belong to the organization.
Skills they kept to themselves	Stay hidden. Nobody else can open, edit or delete them.
Assistant threads	Stay private to them.
Invitations they sent and still pending	No longer open from their link.

Check these after removing someone

• Connections. A connection made with a person’s own account, such as their Gmail, still acts as that account. Check each connection’s account on the Apps page, and disconnect any that shouldn’t stay.
• API keys. If they could have copied a key, revoke it on the API keys page and create a new one.
• Agents using their private skills. An agent that mounts one of their own skills keeps using it. Its editor lists the skill as “A skill you can’t see (deleted, or another member’s)”. Remove it there if the agent shouldn’t keep it.
• Invitations they sent. Cancel each one and invite the person again yourself.
• Notification steps on the Free plan. The Free plan emails only the organization’s members. A Notification step addressed to the removed person fails with “The Free plan emails only the organization’s members”. Change its recipients.

If the person joins again later, their own skills and assistant threads are there again.

Belong to several organizations

One account can belong to several organizations, with a role in each. Open the account menu at the bottom of the sidebar to see them under Organizations and switch between them. New organization starts another one, with you as its owner.