Invitations & offboarding
Membership changes are normal. The goal is to add and remove people without accidentally granting too much access or tying business resources to one employee.
Invite a member
- Open the organization member-management surface.
- Enter or select the intended account identity.
- Choose the smallest appropriate role.
- Confirm seat availability when the plan uses seats.
- Send the invitation.
- Verify acceptance before assuming the member can access organization resources.
Invitation states
An invitation can be pending, accepted, expired, cancelled, or otherwise invalid according to the active implementation.
If an invitation expires, send a fresh one rather than repeatedly reusing an old action.
Change a role
When responsibilities change, update the organization role and then review resource-level permissions and developer credentials separately.
A role downgrade does not automatically prove every independent API credential or project share was removed.
Offboarding checklist
Before removing a member:
- identify organization-owned vs personal projects
- transfer business-critical personal resources where supported
- review organization role and project permissions
- review API keys, applications, service accounts, and integrations associated with the person
- review active automation ownership
- review billing/admin responsibilities
Then remove organization membership.
After removal
Organization-owned projects, Knowledge, billing, applications, and artifacts should remain with the organization.
The former member should no longer receive organization access through membership, but personal Starfire resources remain personal unless separately changed.
Do not delete an account to offboard someone from one organization. Organization membership and the person’s overall Starfire account are different scopes.
