Skip to main content

Members and invites

Administration → Members is the list of everybody in the organization, their role, and their status.

Inviting somebody​

Invite by email address and choose the role they arrive with. They get an email with a link; accepting it creates their account inside your organization. To join, they agree to the Terms of Service and the Acceptable Use Policy and confirm they have read the Privacy Policy. See Legal documents and your data. They don't need to confirm their email separately, because opening the invitation already proves they own the address.

You can't invite anyone until you have confirmed your own email.

An invitation that has not been accepted can be revoked, and a pending invite shows as such in the list rather than looking like a member who never signs in.

The list​

:::note Recently changed The list has a Positions column, and clicking anybody's row opens their profile. Before this, positions were small labels beside the name, and a row did nothing when clicked — the only way to a colleague's profile was through their avatar elsewhere in the app. :::

Each row shows the person, their email, their role, their positions (Tester, Developer — see Inviting somebody), whether they have two-factor set up, and their status. A dash in Positions means none has been set. Clicking a member or a viewer opens their profile; the ⋮ menu at the end of the row is where their role, positions and account are changed. Pending invitations sit in the same list with an Invited or Expired label, and have no profile to open yet.

Seats and viewers​

Two separate allowances:

  • Seats are for people who create and edit — owners, admins and members.
  • Viewer invitations are for guests, and are issued under a weekly allowance that grows with your seat count.

Both come from your plan. See Plans and billing.

The 2FA column​

Every row says whether that person has two-factor authentication set up. Pending invites show a dash — there is no account yet.

The column is visible to everyone who can open this screen, not only to owners and admins.

Resetting somebody's two-factor​

For the person who has lost both their phone and their backup codes. It is the only way back for them.

:::note Recently changed Who can reset whose two-factor is now tiered by role, not a flat owner/admin rule:

  • An admin can reset a member's or a viewer's.
  • Only the owner can reset an admin's.
  • Nobody can reset the owner's from this screen — not even another owner, if your organization has more than one.

An admin who tries to reset another admin, or the owner, gets a specific refusal instead of the option quietly not being there: "Only the organization owner can reset an admin's two-factor authentication", or "The organization owner's two-factor authentication cannot be reset here." :::

Open the row menu and choose Reset two-factor. It costs your password and your own code, because this is the one action in Sekee where one person can weaken another person's account.

What happens to them:

  • Their authenticator and their backup codes stop working.
  • They are signed out everywhere, immediately. If the reason for the reset is that somebody else has their phone, leaving that session alive would defeat the exercise.
  • They set up a new authenticator the next time they sign in.
  • They are emailed about it, whether or not they asked for it.

It is written to the activity log with your name on it. You cannot reset your own — use Profile → Security, which asks for a code and so proves your authenticator still exists.

Removing somebody​

Removing a member takes away their access. What they wrote stays — test cases, bugs, comments and sessions keep their author, because rewriting history to tidy up a leaver's name makes the record useless.

What a member sees​

Everything in the organization. Sekee's tenancy boundary is the organization, not the project: there is no per-project visibility. If you need two audiences who must not see each other's work, that is two organizations.

caution

This is worth deciding early. Projects organise work; they do not isolate it.

While a deletion is scheduled​

If the organization is scheduled for deletion, nobody can be invited. The Invite buttons are disabled and say why, and a pending invite sent before the request stops working. Cancelling the deletion restores both.