Users & Permissions
Every member of an Organization sees its Users tab: a list of members with their Name, Email, Role (Owner, Admin or blank) and Timezone. Admins and the owner also see invitations not yet accepted, with the Role Invited. Email addresses are masked: partly for admins and the owner, fully for other members. Admins and the owner invite users and change other users' access; every user edits their own settings.
User Settings
Open your settings from your name at the top right: choose Edit. On the Users tab, each row's menu has Edit (your own row; admins can edit every row but the owner's, and the owner every row) and Disconnect (remove the user from the Organization; see Permissions).
The dialog has your account fields at the top and your Projects below.
Account
| Setting | Description |
|---|---|
| Username | Your sign-in name. The Admin checkbox beside it (labeled Owner for the owner) shows the user's role; admins and the owner set it for others (see Permissions). |
| Password, Password confirmation | Type the new password in both. |
| Access token | Your personal credential for the Testspace client and the Web API, used in place of your username and password. Copy it with the copy icon; the button beside it generates a new one, and the old token stops working. Keep it secret. |
| First name, Last name | How Testspace shows you: first name and last initial. |
| Email address | Where Testspace sends email. If you sign in with GitHub, Bitbucket or GitLab, you choose from that account's addresses. |
| Time zone | The time zone for dates and times, and for when your Digest is sent. |
| Delete your account | Permanently deletes your Testspace user. Shown only if you don't own an Organization. |
| Leave | Removes you from this Organization. The owner can't leave without first transferring ownership (see Account & Billing). |
If you sign in with GitHub, Bitbucket or GitLab, your username, name and password come from that service and can't be changed here.
Projects
The table lists the Projects you have access to, with two settings for each. The checkbox in a column heading sets that column for every Project.
| Column | Description |
|---|---|
| Notification | Which published Results you get an email for. None: no email. Unhealthy only: every Result that isn't Healthy (Unhealthy or Invalid), the first Healthy Result after one that wasn't, and a Space's first Result. All: every Result. See Health for the verdicts, and Result Email for what the email shows. |
| Digest | A weekly summary of the Project, sent Monday at midnight in your time zone. Projects with nothing new that week are left out. See Weekly Digest. |
Sandbox Spaces don't send result notifications (for example, a branch without an open pull request): see Sandbox.
When a Space misses its publication deadline, an email goes to the same users: everyone whose Notification for that Project is Unhealthy only or All, unless the Project is archived.
When an admin or the owner opens another user's settings, the table lists every Project, with a checkbox column for giving or removing access. Admins and the owner have access to every Project, so their checkboxes are locked.
Project Access
Admins and the owner manage who can use a Project from the Project's options menu: Access. The dialog lists the Organization's users with these columns:
| Column | Description |
|---|---|
| (checkbox) | Whether the user has access to the Project. Locked for admins and the owner, who always do. |
| Users | Name and username. |
| Role | Owner, Admin, or blank. |
| Notification, Digest | The user's notification settings for this Project. |
Invite
Admins and the owner invite users from the Users tab: Invite Users. The button isn't shown when the plan's user limit is reached.
The Invite users dialog has:
- At the top, when the Organization has a GitHub, Bitbucket or GitLab service connection: members of the connected GitHub organizations, Bitbucket workspaces and GitLab groups who aren't in the Organization yet. Check a name to invite them; an email address is required, and is filled in when the service provides one.
- Email addresses: a box for other addresses, separated by commas, semicolons, spaces or new lines.
- Project access: the Projects the invited users get access to.
Click Submit. Each invitee gets an email with a link to join; until then they are listed on the Users tab as Invited, and the row's menu has Resend and Cancel.
The invitation is tied to its email address. An invitee who opens the link while signed in to a different Testspace account sees Your Testspace account doesn't match the invitation: they should sign out and open the link again, or ask for an invitation to the right address.
A user who signs in with GitHub, Bitbucket or GitLab and is a member of an organization connected to the Organization joins it automatically, without an invitation, with access to the Projects of the repositories they can access, when they open the Organization's address or a commit of theirs posts a check. They join even past the plan's user limit, and a plan billed per user is charged for them. See Integrations.
Request Project Access
A member who doesn't have access to every Project sees the Request Project Access button on the Projects tab, and a Request Access link on each Project they can't use. Choose the Projects, add an explanation, and click Submit: the owner and admins get an email. They grant access in the user's settings or the Project's Access dialog.
Permissions
Within Organization
There are three roles:
- Member: uses the Projects they've been given access to.
- Admin: has access to every Project, and manages Projects and users. An Organization can have any number of admins.
- Owner: an admin who also manages the account. Each Organization has one owner.
| Action | Member | Admin | Owner |
|---|---|---|---|
| See the Users tab | ✔ | ✔ | ✔ |
| Edit your own settings and notifications | ✔ | ✔ | ✔ |
| Invite users; set other users' Project access, Notification and Digest | ✔ | ✔ | |
| Make a member an Admin | ✔ | ✔ | |
| Remove Admin from a user | ✔ | ||
| Disconnect a user from the Organization | members only | ✔ | |
| Create, edit and delete Projects; recover deleted Projects; sync a Connected Project | ✔ | ✔ | |
| Account tab: plan, payment, Organization profile, cancel (Account & Billing) | ✔ | ||
| Connect services (Integrations) | ✔ | ||
| Create Spaces (Standalone Projects), edit Space settings, delete Spaces | ✔ | ✔ | ✔ |
| Copy and move Spaces (Standalone Projects); clone and merge Manual Spaces | ✔ | ✔ | ✔ |
| Reset a Manual Space | ✔ | ✔ | |
| Publish Results; comment on, pin and export Results | ✔ | ✔ | ✔ |
| Rename, complete and delete Results | own | all | all |
| Triage a failure on the Space's active Result | ✔ | ✔ | ✔ |
| Notes: create and comment; edit, delete and archive | own | all | all |
| Star a Note | ✔ | ✔ | |
| Add, edit and delete metrics | ✔ | ✔ | ✔ |
| Manual: run test sessions; write specs (Standalone Projects) | ✔ | ✔ | ✔ |
| Manual: edit and complete test sessions | own | all | all |
In a Connected Project, Spaces are created from the repository's branches, and a Space can be deleted only after it is hidden (see Connected Projects). Testspace's built-in metrics can't be deleted.
Outside Organization
A Project's Visibility decides who else can see it: Private, Public or Archived. Spaces follow their Project. An Organization on an open plan has no Private Projects.
| User | Private | Public | Archived |
|---|---|---|---|
| Not signed in | not visible | read-only | not visible |
| Member of another Organization | not visible | read-only; Standalone Spaces can be copied to a Project in their own Organization | not visible |
| Member of this Organization without access to the Project | listed, with Request Access | read-only, with Request Access | not visible |
| Member with access, admin, owner | full use, per role | full use, per role | full use, per role |