Team members
Overview
The Team members page β labeled Users in team management navigation β is where you invite colleagues, assign roles, and control who can work in your team's pursuits, inventory, and settings.
Every person you add can later appear as pursuit owner, questionnaire assignee, SME routing target, or collaboration actor on Team overview. Membership is per team β inviting someone to Team A does not add them to Team B.
Tip: Before inviting, confirm:
You selected the correct active team in the sidebar
Each invitee gets the lowest role that fits their job (usually Collaborator)
Email addresses are typed correctly β invitations bind to that address
You have a plan seat available if billing counts members
Important: Removing a member revokes access immediately. Their past work inside pursuits remains on the team.
How members fit the workspace

Members do not share pursuits across teams. Each team maintains its own list.
How to open
Team management β Management β Users
The compact app sidebar shows Settings and Overview, but not Users. Use the full team management navigation for this page.
Page title on screen: Team members (heading may appear only in the layout header on smaller screens).
Page layout
Header
Add member (plus icon, top-right) opens the invitation dialog.
Pending invitations
When invitations are outstanding, a collapsible card sits above the members table.
Cancel withdraws the invite. While processing: Cancelling.
Success toast: Invitation cancelled β "The destinee will no longer be able to accept it."
Members table
Plain table with sticky header.
Roles
Tendersight uses role-based access within a team. Typical roles:
Owner is a single person per team β not assigned via invitation. See Transfer ownership.
Full matrix: Permissions and access.
Role management
Each member has a button showing their current role:
"No roles" if none assigned
Single role name if one role
"Administrator +2" style if multiple roles
Click to open Member roles β checkboxes for available roles.
When selections change, Save changes appears at the bottom of the dropdown.
Saving opens a confirmation:
Title: "Update roles for {name}?"
Explains which roles were added or removed
Success: Roles updated β "All team members should be able to see the changes now."
Caution: Promoting many users to Administrator widens settings and member-management access for the whole team.
Remove a member
User-minus icon on the row.
Confirmation:
Remove member
"Are you sure you want to remove {name} from this team?"
"They will no longer have access to this team's resources, but all their work will remain untouched."
You cannot remove the last member who can manage the team. Warning toast: Cannot remove member β "The last remaining member of this team who can manage members cannot be removed."
No success toast on removal β the dialog closes and the list refreshes.
Invite new members dialog
Modal with user-plus icon. Title: Invite new members.
Add one invitee
Add (+) β validates and queues the invitee.
Validation runs on Add, not every keystroke:
Queue
Queued invitees list below the form with email, roles, and remove (X).
Footer
Invitee experience
Email link β You've been invited to join a team β team name, prospective roles, Accept / Reject.
See Accept team invitation.
During Create team, wizard invites default to Collaborator β change roles here after they join.
Pagination
Bottom of page: "Showing elements {start} - {end} out of {count} results."
First Β· Previous Β· page numbers Β· Next Β· Last
Changing page loads the next set of members.
Page states
A solo owner still appears as one row β zero members is rare.
Where members matter later
Workflow: onboard a new colleague
Open Team β Users
Click Add member
Enter email; assign Collaborator unless they need admin
Click Invite
Colleague accepts via Accept invitation
Assign pursuit ownership on the kanban as needed
Optionally add to SME assignments

Permissions
Owners and administrators usually manage members; collaborators typically cannot.
Edge cases
What you cannot do
Invite someone as owner (use transfer after they join)
Bulk import members from CSV on this page
See members of teams you do not belong to
Restore removed member's access without re-inviting
Merge member lists across teams
Best practices
Invite with the lowest role that fits the job
Use Administrator sparingly
Cancel stale pending invites
Assign pursuit owners explicitly on the pursuits board
Announce role changes when promoting to Administrator
FAQ
Can one person belong to multiple teams?
Yes. Each team has its own members list.
What if they ignore the email?
Cancel and resend, or send a fresh link from Add member.
Does removing someone delete their pursuit work?
No. They lose access only.
Can I invite during team creation?
Yes β Create team step 2. Roles default to Collaborator.
Who can transfer ownership?
Only the current owner β not from this page.
Troubleshooting
Related articles
Team entity
Team settings
Accept team invitation
Transfer ownership
Create team
Permissions and access
Team overview