> For the complete documentation index, see [llms.txt](https://docs.softwaresecured.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.softwaresecured.com/account/user-management.md).

# User management

When onboarded into the <code class="expression">space.vars.product\_name</code>, only <code class="expression">space.vars.company\_name</code> can assign Org Admins. Once the Org Admins are assigned for the project, they will receive access to <code class="expression">space.vars.product\_name</code> to begin assigning Project Admins and Members.&#x20;

***

### **Roles and permissions**

To ensure the safety and access levels for sensitive information, you must select the roles and permissions for each new user in <code class="expression">space.vars.product\_name</code>.&#x20;

* <mark style="color:orange;">**Org Admin**</mark>

  * Added by <code class="expression">space.vars.company\_name</code>.&#x20;
  * Has all the privileges across all projects.&#x20;

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Multiple Org Admins can be assigned to your Portal tenant. To add more Org Admins, contact <a href="mailto:portal@softwaresecured.com">portal@softwaresecured.com</a>.</p></div>
* <mark style="color:orange;">**Project Admin**</mark>
  * Added by an Org Admin.
  * Has all the privileges for specific projects that they are assigned to.
* <mark style="color:orange;">**Member**</mark>
  * Added by both Org Admins and Project Admins.&#x20;
  * Only has access to the projects that they have been added to.&#x20;

***

### User permission table

The following table lists all the roles and the default granular permissions that can be given to each role.&#x20;

{% hint style="info" %}
Portal supports granular permissions, meaning you can assign any user to only have specific permissions from their role.

For example, you can configure Member 1 to be able to request retests and remove that permission for Member 2, or you could give Project Admin 1 permission to accept risk and remove that permission for Project Admin 2.&#x20;
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th>Add New Users</th><th>Change Project SLA's</th><th>Download Report / Certificate</th><th>Accept Risk</th><th>Request Retest</th><th>Request Consulation</th><th>Fill Checklist</th><th>Remove User</th><th>Manage Integrations</th></tr></thead><tbody><tr><td><mark style="color:orange;"><strong>Org Admin</strong></mark></td><td>✅</td><td>✅</td><td>✅</td><td>✅</td><td>✅</td><td>✅</td><td>✅</td><td>✅</td><td>✅</td></tr><tr><td><mark style="color:orange;"><strong>Project Admin</strong></mark></td><td>✅ <sup><sub>(Own projects only)</sub></sup></td><td>✅</td><td>✅</td><td>✅</td><td>✅</td><td>✅</td><td>✅</td><td>❌</td><td>❌</td></tr><tr><td><mark style="color:orange;"><strong>Member</strong></mark></td><td>❌</td><td>❌</td><td>✅</td><td>❌</td><td>✅</td><td>✅</td><td>✅</td><td>❌</td><td>❌</td></tr></tbody></table>

***

### **Adding users in Portal**

1. In the header, navigate to the user profile menu and click <mark style="color:orange;">**Settings**</mark> (or <mark style="color:orange;">**Users**</mark> if you are a Project Admin).&#x20;

<figure><img src="/files/aSAC5wuNDuIhGf5MHypR" alt=""><figcaption><p>User profile menu on the dashboard</p></figcaption></figure>

2. In the **Team** table, click <mark style="color:orange;">**Add User**</mark>.&#x20;

<figure><img src="/files/Btj7tsXLo2K2bmu9KfF5" alt=""><figcaption><p>Team table section of the Settings page</p></figcaption></figure>

3. Enter an email address and choose the role and projects for the new user.&#x20;
4. **Optional:** Customize each role by adding or removing user permissions as required.&#x20;

   <figure><img src="/files/fEDTne5814Ffs4pWHjFF" alt=""><figcaption></figcaption></figure>
5. Click <mark style="color:orange;">**Add**</mark>.


---

# 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.softwaresecured.com/account/user-management.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.