> For the complete documentation index, see [llms.txt](https://docs.personify.be/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.personify.be/concepts/birth-rights.md).

# Birth rights

This concept in identity management is indicating the fact that identities, based on their attributes ( e.g. belonging to a certain organisation ) are to acquire roles or other relationships by default.

One can make a difference between:

* Role birthrights : based on
  * organisation : if you have a valid assignment to an organisation
  * organisation type
  * identitytype : if you belong to a certain type of identities
  * identity : if you are a specific identity
  * role : if you have a specific role, you automatically obtain another role
  * function: if you have a function
* Organisation birthrights

  * identitytype
  * organisation

It is defined as a scheduler in the schedulers section.

<figure><img src="/files/m5K577PZE45UcfPBjFTL" alt=""><figcaption></figcaption></figure>

Following **configuration** can be changed

| Name               | Description                                                                             |
| ------------------ | --------------------------------------------------------------------------------------- |
| organisationFilter | the organisation for which this scheduler is intended for ( required )                  |
| entitlements       | the list of entitlements that has to be assigned to the targets (required)              |
| identityFilter     | the email address of the identity for which this scheduler is intended for ( optional ) |

So a valid configuration for giving all identities have a organisation assignment with organisation with code AAA a entitlement with code BBB would be:

```
{ 
    "Birthright configuration one": 
    {
       "entitlements" : ["BBB"], 
       "organisationFilter" : "AAA" 
    }
 }
```

{% hint style="info" %}
The scheduler will only create a entitlement assignment when there is not yet any found for the entitlement code.  It will not extend existing or expired assignments
{% endhint %}

Giving a specific person with email *<homer@springfield.com>* entitlement YYY and ZZZ within organisation AAA

```
{
  "Birthright configuration specific identity" : 
     { 
        "entitlements" : ["YYY","ZZZ"], 
        "organisationFilter" : "AAA", 
        "identityFilter" : "homer@springfield.com" 
     }
 }
```

{% hint style="info" %}
The end date of the assignment is calculated based on the value of the attribute **defaultDurationInMonths** of the entitlement specified
{% endhint %}


---

# 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.personify.be/concepts/birth-rights.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.