> For the complete documentation index, see [llms.txt](https://timberid.gitbook.io/timberid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://timberid.gitbook.io/timberid/user-guide/administration-guide/managing-users.md). # Managing Users ### Roles and Permissions TimberID has three different roles. Regular users are called Organization Members. All users must belong to an Organization. Beyond regular users, there are two types of Aministrators, Site Administrators and Organization Administrators. These are described below.
User Role TypeAbilitiesHow to Create
Site AdministratorApprove New Organizations
Approve New Users
Remove Users
Assign Site Administrator Role
Assign Org Administrator Role		Only existing Site Administrators can assign this role to new users.
See a TimberID admin for help
Organization AdministratorApprove New Users
Remove Users
Assign Org Administrator Role		Org Adminsitrators are created when an Organization is first created and may be assigned by an existing Site or Org administrator.
Organization MemberCan see all sample data in TimberID and use the Earth Engine API to load data in PythonSign Up with a particular Organization and have an Organization Admin or Site Admin approve you.
### Assigning Roles To change the role of an existing user, navigate to the All Users screen and select the dropdown to assign a role.
--- # 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://timberid.gitbook.io/timberid/user-guide/administration-guide/managing-users.md?ask=&goal= ``` `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.