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

# Access Requests

When a project is **discoverable**, any organization member can find it in the **Organization Projects** tab on the [Projects page](https://app.cogram.com/dashboard/projects/) and request access to it. Access requests are managed in [Organization Settings > Projects > Access Requests](https://app.cogram.com/dashboard/settings/admin/projects/request-access).

This page covers three things: reviewing pending requests, choosing who can grant access, and routing new requests to an external email.

## Reviewing pending requests

Open requests appear under **Pending requests** at the top of the Access Requests section. For each request you can:

* **Approve**: adds the requester to the project as a member.
* **Decline**: rejects the request. You can include a reason. The requester is emailed that their request was declined.

Pending requests always appear here for anyone who can grant access, regardless of the notification settings below. Turning notifications off never causes a request to be lost.

If a requester gains access another way before you act on it (for example, you add them to the project directly or add them to a [group](/administration/groups.md) that already has access), their pending request clears automatically and its notification is removed. There's nothing left to approve.

Requests you never act on expire on their own after 7 days and drop off the list, so the inbox doesn't fill up with stale entries. Expired requests send no email either way.

## Who can grant access

By default, only org Admins and Owners can approve or decline access requests. To let project owners handle requests for their own projects:

1. Go to [Organization Settings > Projects > Access Requests](https://app.cogram.com/dashboard/settings/admin/projects/request-access).
2. Toggle **Allow project owners to grant access** to on.

| Setting           | Effect                                                                                                     |
| ----------------- | ---------------------------------------------------------------------------------------------------------- |
| **Off** (default) | Only org Admins and Owners can grant access and receive new-request notifications.                         |
| **On**            | Project owners can also grant access to their own projects and receive new-request notifications for them. |

## Access request routing

By default, each new access request notifies your org Admins and Owners. If you manage access through an external workflow (for example, a ticketing system), you can route requests to an email address and, optionally, stop notifying Admins and Owners.

### Send requests to an external email

1. Go to [Organization Settings > Projects > Access Requests](https://app.cogram.com/dashboard/settings/admin/projects/request-access).
2. Under **Access request routing**, enter an address in **Routing email**, for example your ticketing system's intake inbox.
3. Select **Save**.

Each new access request is then emailed to that address. Most ticketing systems turn an inbound email into a ticket automatically, so requests land directly in your queue. Leave the field blank to disable routing.

Once your team grants access outside Cogram, the Cogram-side request stays under **Pending requests** until it's resolved. If granting access adds the person to the project or to a [group](/administration/groups.md) that has it, the request clears itself. Otherwise, leave it and it expires on its own after 7 days.

Cogram sends these emails from its notification address, `noreply@email.cogram.com`. Make sure your ticketing system accepts mail from that sender, otherwise requests may be filtered as spam.

### Notify org admins and owners

The **Notify org admins and owners** toggle controls whether Admins and Owners are alerted about new requests.

| Toggle           | Result                                                                                                                                  |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **On** (default) | Admins and Owners receive an in-app notification and an email for each new request.                                                     |
| **Off**          | Admins and Owners receive neither. Requests still appear under Pending requests, and are still sent to the routing email if one is set. |

> **Note:** The toggle covers both the in-app notification and the email. When it is on, an individual admin still only receives the email if they have not muted "Approvals & Requests" emails in their personal [Notification Settings](/settings/notifications.md). The org toggle is the master switch.

## Next steps

* [Project Management Permissions](/administration/project-management-permissions.md): set project discoverability defaults.
* [Organization Notification Settings](/administration/notifications.md): control notifications across your organization.


---

# 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.cogram.com/administration/access-requests.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.