Organizations
The three organization roles, inviting people, what happens to an invitation over its seven days, and transferring ownership
An organization is the account: billing, the projects, the people, and the invoices all belong to it. Every user belongs to exactly one.
The three roles
Every member of an organization holds one of three roles.
| Role | What it means |
|---|---|
| Owner | One per organization. Everything an Admin can do, plus transferring ownership. The Owner's own role cannot be edited in place. |
| Admin | Invite, remove, and re-role members. Manage custom roles. Read and export the audit log. Cancel or resume the subscription. Buy credits. Rename the organization. |
| Member | Use the projects they are on. Can still start the paid path, create a project, view invoices, and open the payment portal. |
Two things about this list surprise people:
- Members are not locked out of billing. A Member can start the organization's paid path, create a project, view invoices, and open the payment portal to change the card. Creating a CORE project inside the free tier is not a purchase. See Billing for the exact split.
- Owner and Admin writes require two-factor authentication. Inviting, removing, re-roling, editing custom roles, transferring ownership, and reading the audit log all refuse a session that did not use it. Members are exempt. See Accounts and access.
The organization role is separate from what you can do inside a given project. That second layer is covered in Permissions.
Inviting someone
Owners and Admins only. Members see a Restricted panel here.
- Open Settings, then Users & teams (
/settings/users-teams). - Click Invite member.
- Enter the email address. First and last name are optional.
- Choose the role: Admin or Member. You cannot invite someone as Owner.
- Click Send invite.
The person appears under Pending invitations until they accept.
If the invitation email fails to send, the invitation itself still exists and Struxen tells you so rather than claiming success. The row stays in the table so you can resend it.
What happens over the next seven days
| Event | Effect |
|---|---|
| Invitation issued | Valid for seven days |
| Invitee clicks the link | They set a password of at least 12 characters and join |
| You click Resend | Reissues the same link with the original expiry. Capped at 3 resends per invitation per 24 hours. |
| The invitee requests a new link from the expired-link page | Issues a fresh seven days. Capped at 1 per hour. |
| You cancel the invitation | The link stops working |
A resend does not extend the expiry. This is the single most common frustration with invitations. If an invitation has already expired, resending it sends the same dead link. Tell the person to open the link they have and use the request-a-new-one option on the page it lands on.
Changing someone's role
- Open Settings, then Users & teams.
- Click the person's row.
- Under Administrative actions, pick the new Role and confirm.
You can move people between Admin and Member. The Owner's row is not editable here: the modal says so and points you at ownership transfer instead. You cannot change your own role.
Removing someone
Open the person's row and click Remove from organization. This revokes their access to every project in the organization.
Transferring ownership
Only the current Owner can do this, and the session must have used two-factor authentication.
Ownership transfers to any member of the organization, not only to an Admin. When it lands:
- The target becomes Owner.
- The outgoing Owner becomes Admin, and can then be re-roled or removed by the new Owner.
- There is always exactly one Owner.
The three changes commit together. A transfer either happens completely or not at all, so the organization is never left with two Owners or none.
Renaming the organization
Owners and Admins can rename from Settings, then Organization
(/settings/organization). The name is capped at 120 characters. It is the name
that appears on invitations and in the app; it does not change the legal name on
your invoices, which is set on the billing profile.
Seats
The Users & teams page shows a member count against a seat limit. The seat limit is not enforced. Inviting past it works. Treat the number as informational until the seat model ships.
Custom roles
Owners and Admins can define named permission sets beyond the three built-in
project roles, from Settings, then Roles & permissions
(/settings/roles). Two permissions can never be granted through a custom role:
deleting a project and managing the project team. Those stay with the built-in
roles. See Permissions.
The audit log
Owners and Admins can read the organization's audit log at Settings, then
Audit log (/settings/audit-log), filter it by action, actor, and date
range, and export the result as CSV. Retention is two years for every
organization. See Privacy and data.
Deleting an organization
There is no working self-service path to delete an organization. If you need one closed, email support@struxen.io from the Owner's address.
Cancelling the subscription is a different thing and does have a self-service path. It suspends the organization's projects and starts a 30-day clock before they are purged. See Billing.