# Authentication and Security

## Authentication

If you are only using Verb for API collections please select “API Collections Only” so that the authentication method will only require response mapping values that will be used to define Data Access Key parameters and in the Row Level Security configuration. 

The Response Mapping Properties only need to contain the information that will be used to segment data. For example, Most Verb user’s use values such as  Organization, Role and/or User ID. 

You will select the Property Type to configure the values allowed when creating a Data Access Key.

{% hint style="warning" %}
If you are using Verb for both Visual and API Collections please refer to the Authentication Endpoint documentation. 
{% endhint %}

{% content-ref url="/pages/-MQxayitCi2sQ-Le45fP" %}
[Authentication](/environment-settings/authentication.md)
{% endcontent-ref %}

## Row Level Security

You will set the segmentation rules by using the row level security configuration on any table(s) in your model. With the relationship paths drawn, row level security rules will apply from one table across the model to all tables that it is related to. 

Using the Response Mapping Properties set on the authentication method you'll be able to create as simple or complex row level security rules necessary. 

To create row level security rules, open a table options panel and select Row Level Security. Here is where you set the rules. <br>

![A simple row level security configuration](/files/-MV2zO5sgRHhcMFeb1V4)


---

# 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.verbdata.com/collections/api-collections/getting-started/authentication-and-security.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.