Members
- Who can use it
- Org admin (managers see the list read-only)
- Where
- Admin → Members
Members is the list of everyone who can sign in to your workspace, with their role and approval state. Org admins use it to approve people, change roles, invite colleagues and remove access. Managers can open the page and see the list, but cannot change anything.
How people join
Members of your GitHub org join as Developer when they sign in with GitHub. Whether they can see data straight away depends on the approval setting below.
You can also invite people before they sign in, with an invite link or an email invitation. See Invite people.
Approve a join request
When New members wait for approval is on, a verified org member who signs in appears in the list as Pending approval. The page shows how many are waiting.
- Go to Admin → Members.
- Find the person with the Pending approval status.
- Click Approve.
They join as a developer. Approval is recorded in the audit log.
Require approval for new members
- Go to Admin → Settings.
- In Visibility and joining, tick New members wait for approval.
- Click Save settings.
On, verified org members who sign in join as pending until an org admin approves them. Off, they join as developers straight away. The setting applies to people who join by signing in with GitHub.
Change a role
There are three roles: Admin, Manager and Developer. See Roles for what each can do.
- Go to Admin → Members.
- In the Role column, open the menu for the person and pick a new role.
Changing a role signs the member out on devices that use this workspace. They sign in again with the new role.
Hand the admin role to someone else
- On the person’s row, click Make admin….
- Read the confirmation, then click Transfer admin role.
The person becomes an org admin and you become a manager. You are signed out and sign in again with the new role. Both changes are recorded.
A workspace always keeps at least one active org admin. DevGlimpse refuses any change that would leave it without one.
Sign out or suspend a member
- Sign out ends the person’s sessions in this workspace. They can sign in again.
- Suspend… removes their access. They are signed out and cannot sign back in until you let them back.
A suspended GitHub member returns by signing in again as a verified member of your GitHub org. Someone you invited by email returns when you invite their address again. The last org admin cannot be suspended.
Invite people
You create invitations at the bottom of Admin → Members.
Invite link
Use this for colleagues who are in your GitHub org.
- Under Invite team members, click Create invite link.
- Copy the link and send it to your colleagues.
Each link works for seven days. Whoever opens it signs in with GitHub and joins as a Developer, never higher. The list shows each link as Active, Expired or Revoked.
To cancel a link before it expires, click Revoke on its row. Anyone who opens it afterwards is turned away.
Invite by email
Use this for colleagues without a GitHub account.
- Under Invite by email, enter the Email address and pick a Role.
- Click Send invitation.
They get a one-time sign-in link by email and join with the role you chose. The link works once and expires after 15 minutes. The invitation stays open for seven days, and the person can ask for a new link on the sign-in page while it is open. Statuses are Pending, Joined, Expired and Revoked. Click Revoke to cancel an invitation.
If an address already received three sign-in links in the last 15 minutes, the invitation is saved but no email is sent. The person can ask for a link on the sign-in page later.
When someone leaves your GitHub org
When GitHub reports that a person was removed from your org, DevGlimpse suspends their membership. They lose access to the workspace. Their past activity stays in your reports unless you exclude or erase them.