> 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/technical-notes/well-seeker-pro-technical-notes/products-and-features-and-user-permissions-update.md).

# Products & Features and User Permissions Update

Details an update to the user management Products & Features and User Permissions systems in the Innova Web Portal and the Innova Phone App.

## Background

Some administrators expressed a desire to be able to assign role access to certain pages and features within the Web Portal and App, that were only available when the Admin feature was assigned to a role, but not allow that same role to have access to other Admin pages and features, e.g., have access to the Data QC feature, but not have access to the User Management feature.

As of 12th April 2024, we have tackled this request with an update to the user management Products & Features and User Permissions system.

## Description

Roles are now simpler to define. All of the old **base feature** options have been moved into the products and features section. Any features that were previously locked behind the Admin user permission, have also been moved and are now selectable within the products & features section.

The only visible changes that a user will see are in the Roles & Profile pages. The **Base Features** option has been removed and the **Products & Features** selection interface has been updated to make selection of the larger number of products & features simple.

<img src="https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FM2zqJFVHDYuXg4DJMnVc%2F0.png?alt=media" alt="" width="240">

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FKYYrU8vS75jRYaJXU3Nd%2F1.png?alt=media)

In the **Roles** section the **Admin** user permission no longer gives access to specific products and features. However, it is required to carry out any of the below actions within the Web Portal and App; so while a user may have access to some of the below features, they will not be able to use all/some of the actions within them, unless their role has Admin permissions enabled:

* Bulk Edit
* Delete Field
* Delete Operator
* Update / Delete Activity Code
* Update / Delete Phase Code
* Update Third Party app credentials
* Update Anti-Collision Dashboard settings
* Reset Component Catalog
* Component Catalog Create/Edit/Delete

![](https://100379801-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-McEwHTOM_v4MexTVGSe%2Fuploads%2FTWKzBCVzm4MXjZ3zConZ%2F2.png?alt=media)


---

# 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.innova-drilling.com/introduction/technical-notes/well-seeker-pro-technical-notes/products-and-features-and-user-permissions-update.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.
