> For the complete documentation index, see [llms.txt](https://docs.bluepro.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluepro.ai/team-and-admin/team-permissions-and-time/managing-team-members-and-branch-access/managing-team-members.md).

# Managing team members

Keep team records accurate as people join, move branches, or leave the company. Clean staff setup helps with scheduling, permissions, payroll, and reporting.

### Steps

1. Open the staff or team member area in BluePro.
2. Update the person’s details, branch access, or status.
3. Save the changes and confirm they can access the right work.

### Tips and notes

* Remove old access quickly when someone leaves the business.
* Review branch access whenever a role changes.

### Related articles

* [Understanding permissions](/team-and-admin/team-permissions-and-time/understanding-permissions-and-roles/understanding-permissions.md)
* [Inviting users and assigning roles](/team-and-admin/team-permissions-and-time/understanding-permissions-and-roles/inviting-users-and-assigning-roles.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bluepro.ai/team-and-admin/team-permissions-and-time/managing-team-members-and-branch-access/managing-team-members.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.