> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation/content-library/writeupsdb/managing-users.md).
# Managing Users
If the repository is not an "Open" type repository, admins can manage users by clicking Users & Permissions.
## Adding Users
Step 1: From the **Repositories** tab of the **WriteupsDB** home page, click the card of the repository to modify.
Step 2: Click **Users & Permissions**.
Step 3: Click **Add User**.
Step 4: Type in the user from the pulldown menu and select the permission. Repeat as necessary. Click **Add X Users**.
Step 5: Edit the permission or delete a user, if needed. Click **Done**.
## Modifying Users
Step 1: Select the desired repository card from the **WriteupsDB** home page and click **Users & Permissions**.
Step 2: Select the user to modify and change permissions from the pulldown menu.
Step 3: When finished, click **Done**.
## Deleting Users
Step 1: Select the desired repository card from the **WriteupsDB** home page and click **Users & Permissions**.
Step 2: Select the user to remove and click the **X** in that row.
Step 3: When finished, click **Done**.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.plextrac.com/plextrac-documentation/product-documentation/content-library/writeupsdb/managing-users.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
