# Scope

Scope is a parameter as defined in the OAuth 2.0 standards (RFC6749) to enable a client to specify the scope of the access request. The value of the scope parameter is expressed as a list of space-delimited, case-sensitive strings although some implementations of scope uses a comma-delimited format. Scopes limit access for OAuth2 tokens and do not grant any additional permission beyond that which the client already has.

Scopes apply to applications only. Scopes play a crucial part in defining the ultimate access to a resource by a User.

User’s Roles / Permissions + Claims + Application Scopes

### Naming Conventions <a href="#conventions" id="conventions"></a>

Turium Enigma services follow these standard naming conventions for scopes.

```
Template: {resource}.{optional subresource}.{action}
Examples: mileage.rate.read
          receipts.read
```

### List of v4 Actions <a href="#actions" id="actions"></a>

`{actions}` are common authorizations across resources.

<table data-full-width="false"><thead><tr><th>Action</th><th>Description</th><th>Examples</th></tr></thead><tbody><tr><td><code>read</code></td><td>Read only access (GET)</td><td><code>receipts.read</code>, <code>budgetitem.read</code></td></tr><tr><td><code>write</code></td><td>Read AND Write access (GET, POST, UPDATE etc)</td><td><code>company.write</code>, <code>travel.receipts.write</code></td></tr><tr><td><code>writeonly</code></td><td>Write only access</td><td><code>mileage.journey.writeonly</code>, <code>receipts.writeonly</code></td></tr><tr><td><code>delete</code></td><td>Delete access</td><td>N/A</td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.turium.ai/home/enigma/authentication/scope.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.