A Team invitation adds a person to a Scylla organization. Membership and licensing are related, but they are not the same thing.
The clean mental model is:
Invitation
→ Membership
→ Seat assignment
→ Desktop Team activation
A person can be a member of the organization before a Team seat has been assigned.
Who manages invitations
Organization management is available from the authenticated Scylla Workbench Team console.
The actions visible to you depend on your organization role. Scylla organizations use roles such as Owner, Admin, and Member.
Do not assume that every member can invite, remove, or change another member.
Send an invitation
If your role allows invitation management:
- Sign in to the Scylla Workbench Team console.
- Open Members.
- Choose the invitation action.
- Enter the person's account email.
- Select the intended role if the UI allows role selection at invitation time.
- Send the invitation.
The invitation should remain visibly pending until it is accepted, canceled, or expires according to the current service behavior.
Accept an invitation
The invited person should:
- Open the invitation using the intended Scylla Account.
- Sign in or create that Scylla Account if necessary.
- Accept the organization invitation.
- Return to the Team console and confirm that the organization is visible.
Accepting the invitation establishes membership. It does not necessarily assign a Team seat.
Pending invitations
Pending invitations should be treated as organization state, not as active members with a valid Team entitlement.
If a person has not accepted yet:
- do not count on desktop Team activation;
- do not assume Team Memory is available to that person;
- do not treat the invitation as a seat assignment.
If your role allows it, use the Team console to resend or cancel a pending invitation.
Roles
Use roles to describe organization responsibilities, not to replace Scylla desktop Policy.
For example, being an Admin in the Team console can allow account-level administrative work. It does not automatically mean an Agent running on that Admin's desktop may bypass Scylla Policy.
Organization role and Agent authority are separate concepts.
Invitation vs seat
This distinction is important:
Invitation / membership answers:
Is this person part of the Scylla organization?
Seat assignment answers:
Does this member currently have a Team license entitlement?
A new member may appear correctly in Members while the desktop still reports that no Team seat is assigned.
Continue with Seat Assignment.
No seats available
If the organization has no unassigned seats:
- Complete or verify the invitation normally.
- Leave the person as a member without an assigned seat.
- Have an authorized organization administrator adjust the purchased seat quantity if appropriate.
- Assign the newly available seat after billing state becomes authoritative.
Do not assume that returning from a checkout screen immediately changes entitlement state.
See Billing.
Removing a member
Removing a member is consequential.
Before removing someone, consider:
- their assigned Team seat;
- active desktop installations;
- organization access;
- Team Memory access;
- whether the person still needs data or work-product handoff.
Removing a member should not delete their local project files from their own computer.
Common problems
Invitation sent to the wrong email
Cancel the pending invitation if your role allows it, then invite the correct Scylla Account email.
Invitation accepted but no Team license
Assign a seat separately.
Member cannot see the organization
Confirm the invitation was accepted using the same Scylla Account currently signed in.
Invitation is pending for a long time
Confirm the recipient received the correct invitation and is signing in with the invited address. Resend or cancel/reissue if the Team console provides those actions.