> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/settings/add-a-specialist-from-a-pre-filled-link.md).

# Add a Specialist from a Pre-Filled Link

Open the **Add Sprinto Specialist** drawer with a Specialist's details already filled in, straight from a link — instead of opening the drawer and typing their email and name by hand.

A Specialist is added from **Settings > Sprinto Support > Specialists**, using the **Add specialist** button. A link to this page can now carry the Specialist's email, first name and last name (and, where your organisation uses Access Roles, a suggested access role) so the drawer opens ready for you to check and confirm.

{% hint style="info" %}
The link only fills in the form. It never adds the Specialist by itself — you still review the details and confirm before anyone gets access.
{% endhint %}

***

#### 1. Open the drawer from a link

When you open a link to **Settings > Sprinto Support** that carries a Specialist's details, the **Add Sprinto Specialist** drawer opens automatically with the **Specialist email**, **First name** and **Last name** fields already filled in.

An information banner appears at the top of the drawer to flag that the form was pre-filled:

> These details were filled in from a link. Check them before adding the specialist.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FvWoe4CVTekUyPe0holEW%2Fpi-20438-s1-prefilled-drawer.png?alt=media" alt="The Add Specialist drawer under Settings > Sprinto Support, opened from a deep link. The Specialist email, First name (&#x22;Daniel&#x22;) and Last name (&#x22;Okafor&#x22;) fields are pre-filled, and a highlighted informational banner reads: &#x22;These details were filled in from a link. Check them before adding the specialist.&#x22;" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
If your organisation uses Access Roles, the link can also suggest an access role by name. When the name matches one of your organisation's existing roles exactly (ignoring case and spacing), that role is preselected in the Access Roles picker and the banner changes to mention it too: "This form was filled in from a link, including the access roles. Check everything before adding the specialist." A name that matches no role, or more than one, selects nothing — you pick as usual. The role suggestion never applies to a system role such as Admin.
{% endhint %}

***

#### 2. Review and confirm

Check every pre-filled field before going further — the link's details are a starting point, not a guarantee:

1. Confirm the **Specialist email**, **First name** and **Last name** are correct, and edit any of them if needed.
2. If an access role was suggested, confirm it's the right one. Selecting a different role replaces the suggestion; clearing it doesn't bring it back.
3. Continue and finish adding the Specialist as you normally would.

{% hint style="info" %}
The usual rules for adding a Specialist still apply to a pre-filled form — for example, a personal email address is refused even if it came from the link.
{% endhint %}

***

#### Opening the drawer without a link

The **Add specialist** button on the Specialists tab still opens the same drawer, empty and with no banner, exactly as before. The pre-filled drawer is an additional way in, not a replacement.

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2Fp4siGGBUsZOaJu3NguKQ%2Fpi-20438-s5-plain-drawer.png?alt=media" alt="The same Add Specialist drawer opened the ordinary way, via the Specialists tab&#x27;s &#x22;Add specialist&#x22; button. Its title &#x22;Add Sprinto Specialist&#x22; is highlighted. The Specialist email, First name and Last name fields are empty and no banner is shown, contrasting with the pre-filled, deep-linked state in the previous screenshot." width="563"><figcaption></figcaption></figure>

***

#### FAQs

<details>

<summary>Does opening the link add the Specialist automatically?</summary>

No. The link only fills in the form. Someone still has to review the details and confirm before the Specialist gets access.

</details>

<details>

<summary>What happens if the suggested access role doesn't match anything in my organisation?</summary>

Nothing is preselected, and you choose a role as you normally would. This also applies to a role name that matches more than one of your organisation's roles, and to a system role such as Admin, which is never suggested from a link.

</details>

<details>

<summary>Can I change a role the link suggested?</summary>

Yes. Selecting a different role in the picker replaces the suggestion, and clearing the picker doesn't bring the suggested role back.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sprinto.com/settings/add-a-specialist-from-a-pre-filled-link.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
