> For the complete documentation index, see [llms.txt](https://docs.innova-drilling.com/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.innova-drilling.com/introduction/innova-engineering-how-to-guides/vantage-guides/providing-3rd-party-access-to-your-organizations-server-data.md).
# Providing 3rd Party Access to Your Organizations Server Data
## 1.0 - Introduction
Your organization may wish to give third parties permissions based access to your server database data, so that they can view progress on drilling projects etc., via Vantage. To do this in a way that keeps your data secure and that respects the confidentiality of other clients, third party levels of access must be controlled.
The User Management section in Vantage contains options that allow you to customize the level of access for users viewing your organization’s data. Users can have their access customized in the following ways:
* Their permission to create new data, and edit or delete existing data. Removing all permissions turns the user into a ‘**view only**’ user, who can view data but not edit it.
* Their access can be restricted so that they can only view data for specific operators or wells.
* Their access to Products & Features can be restricted.
There are 2 different ways a third party user can be given access to a database:
* The first way is to create a new user within your organization and assign the appropriate role to this user. In this situation, everything about this user is controlled by you as a company administrator.
* The second way is to provide access to a user who already has login credentials for a different company. For example, an Operator may already have their own server database, where they have logins for all the appropriate members of their team. In this situation, it is possible to provide access to your companies database to one or all of these users. When doing this, the admin will assign an appropriate role and can restrict access to wells and features, but overall management of this user is controlled by their own admin.
This document will guide an admin through the process of adding a user in both of the above scenarios.
**Note: To perform the steps in this guide, you must be logged into the Web Portal as a user that has Admin permission and access to the User Management feature. To check your available features and permissions, click on the click on the Account Settings icon in the top right of any page and select Profile.**
## 2.0 – Creating a Restricted Role
User access is controlled through the creation and assignment of roles. A role is a set of user permissions that can be applied to multiple users. Follow the below steps to create a customized view only role that can then be applied to any user in your organization, and also any user from outside your organization:
1. Click on the icon in the top left to open the main menu.
2. In the main menu, scroll to the bottom and click on **User Management,** then click on **Roles.**
This will open the User Roles page.
3. Create a new role by clicking in **Add Role** in the ribbon menu and filling in the fields in the dialog:
1. Enter a name for the new role in the **Name** field.
2. Give your role a brief description in the **Description** field
3. Check the desired permissions for that role.
4. Once you have filled in all fields, hit **Create** and the new role will be automatically added to the list. If you need to edit a role, select it by left clicking on it and then select **Edit** in the ribbon menu.
5. Left click on the role to select it, and then select **Operators** in the ribbon menu.
6. Restrict the operators that the new role can access by checking **ON** the operator(s) that you want to grant access to, while leaving the others toggled **OFF**. In this example, we are allowing the role to only view data related to the operator ‘Black Oil & Gold, LCC’. Click on **Apply** to save your settings. **Note: Leaving all operators checked OFF will allow the role to access ALL operators.**
7. Click on the role to select it again, and select Products & Features
8. Choose which features the new role will have access to in Vision, Vantage, API, Well Seeker and Vantage Data Link by checking the checkboxes in their respective columns.\
If you allow access to any features in a column, you must also check the **Base** feature at the top of each column.
**Note:** Toggling off the **Base** feature available for Well Seeker will prevent the user from logging into your organization’s server database via Well Seeker. This is recommended if you are setting up a viewer only user, as the permissions defined in step 4 do not apply to Well Seeker. Access to other features in Well Seeker are controlled by the user’s license and cannot be restricted via Roles. The assigned operator access will apply when the user logs into your organization’s remote server database via Well Seeker.
9. Click on the **Apply** button in the Products and Features window to save your settings. Setup of the view only and operator restricted role is now complete. The next step is to assign the role to a user.
## 3.0 – Assigning the Role to a User
Now that the customized view only role has been created, it needs to be applied to a user.
### 3.1 – Assigning to an Existing User
1. Click on the  icon in the top left of the page to open the main menu. You can also access the Users page by clicking on Users option in the ribbon menu of the Roles page
2. In the main menu, scroll to the bottom and click on **User Management,** then click on **Users.**
This will open the Users page.
3. Left click in the Role for the existing user and select Edit in the ribbon menu to open the Edit User dialog where you can change the role users role. This is why it is important to name your roles appropriately, as this list may have quite a number of options available to choose from.
4. When the user next logs into Vantage, they will now be restricted to the operators and features permitted by their Role. They will also not have permission to make any changes to the data in the database.
### 3.2 – Creating a New User and Assigning a Role
1. Click on the  icon in the top left to open the main menu.
2. In the main menu, scroll to the bottom and click on **User Management,** then click on **Users.**
This will open the Users page.
3. Create a new user by clicking on **Add User** in the ribbon menu and filling in the fields in the Add User dialog.
1. Email: Enter an email address for the new user in the Username field. The username must be a valid email address.
2. Role: Select the restricted role that you created from the dropdown list.
3. Units: select the default unit set for the new user. They can change this themselves after they log in.
4. Group: Select the desired group in the dropdown list.
5. Type the password and check the **Require Password Reset** option if you wish the user reset their password in the first access.
Left click on the User and select **Edit** in the ribbon menu to open the Edit User dialog where you can change the users details
4. Once all of the required fields have been filled in, the new user will automatically be added to the list of users for your organization.
5. When the user logs into Vantage, they will now be restricted to the operators and features permitted by their Role. They will also not have permission to make any changes to the data in the database.
## 4.0 - Additional Access Tools in the Users Page
Once a user has been assigned a role in the Users page, they can be granted access to additional operators beyond those defined by their role. They can also be restricted to specific wells, if required. To do so, follow the below steps:
### 4.1 – Access to Additional Operators
1. In the Users page click on the desired user and select **Operators** in the ribbon menu.
2. Toggle **ON** operators that you want the user to be able to access. Click on Apply to save your changes. The chosen operators will be **added** to the permitted operators granted by the user’s role. In this example, the user’s role grants access to Black Oil & Gold, LLC, but this specific user has also been granted access to Venture E\&P and Gold Resources.
3. Click on **Apply** to save your changes.
### 4.1 – Well Restriction
1. In the Users page, click on the desired user, and select **Wells.**
2. This will display a list of all wells contained under the operators that the user can access. The list can be filtered by typing in the search bar at the top of the list.\
By default, the wells will all be toggled **OFF**. When this is the case, the user has access to **ALL** wells under the operators permitted by their role.\
To restrict access for the user, toggle the wells you want them to be able to access **ON**. The user will now only be able to access wells that have been toggled on, and will not be able to access any wells that are toggled off.
3. Click on **Apply** to save your changes.
## 5.0 – Database Access
The Database Access page allows you to grant **users from other organizations** access to your organization's server database, using Vantage. To grant a user access to your organization's server database, follow these instructions:
1. Click on the  icon in the top left to open the main menu.
2. In the main menu, scroll to the bottom and click on **User Management,** then click on **Database Access.**
3. Enter a valid username from another organization into the **UserName** field at the bottom of the page. Note, that if the email address used here is not being used within another Organizations user management, then this process will not work.
Alternatively, you can grant access to all users registered under another organization by entering the organization's name. For example, typing **Innova** would grant access to all users in the Innova organization. This option removes the requirement to add lots of individual usernames, and ensures any new users are granted access automatically. Contact Innova directly to find out the correct nomenclature for any required organization.
4. In the **Organization** field, select the organization that you want to grant the user access to. In most cases, you will only have your own organisation as an option here.
5. In the **RoleId** field, choose the role that you wish to grant the user when they are viewing your organization.
6. If the user is successfully added, a row will be added to the table displaying their username and their source organisation to the page. Click on the icon to expand the user, displaying the organisation(s) that they have access to.
Each row in the expanded section displays the following:
**Organisation:** The organisation that the user has been granted access to.
**Role:** The role the user has when accessing the organisation.
**Access Granted By:** The name of the admin in your organisation that gave the user access.
**Access Granted Date:** The date this user was granted access.
**Delete:** Clicking on the dustbin icon will revoke the user’s access to the organization.
Once a user has been granted access to your organization’s server data, they will able to view wells from both their organization and yours on their Wells List page, when logged into Vantage.
For other pages, they can switch between their organization and yours by clicking on the  icon in the top right of every page.
---
# 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.innova-drilling.com/introduction/innova-engineering-how-to-guides/vantage-guides/providing-3rd-party-access-to-your-organizations-server-data.md?ask=&goal=
```
`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.