# What You Can Access

Learn how your organization's package decides which screens you can open, and what the Admin and Member roles can do.

Source: https://docs.deepinfo.com/guide/basics/packages-and-roles/

Last updated: 2026-09-26

---
Two things decide what you see in the platform: your organization's **package**, which includes modules
and features, and your **role**, which is either Admin or Member.

## Before You Start

This applies to every user. To find out which package your organization has, ask an admin in your
organization or [support@deepinfo.com](mailto:support@deepinfo.com).

## Where to Find It

Package locks appear on the module pages themselves. Roles are managed on the **Members** page (admins
only): **Sidebar:** **SETTINGS** › **ORGANIZATION SETTINGS** › **Members** ·
https://platform.deepinfo.com/app/settings/org-members

## Packages

Your organization's package is what it has bought from Deepinfo. It decides which modules and features
open. The sidebar shows every module either way: a module outside the package opens to a lock screen
instead of its content.

### Lock Screens

A locked screen takes one of three forms:

- **Full-page lock.** The page is replaced by a message that the module
  **IS NOT INCLUDED IN YOUR PACKAGE** (for example **DARK WEB SEARCH IS NOT INCLUDED IN YOUR PACKAGE**),
  the line "Please talk to us to upgrade your package." and a **TALK TO US** button.
- **In-page lock.** The page stays visible but faded and cannot be clicked. Over it are the line
  "This module is not included in your package." and a **TALK WITH AN EXPERT** button.
- **Faded content.** The content is shown faded and cannot be clicked, without a message.

**TALK TO US** and **TALK WITH AN EXPERT** both open an e-mail to
[support@deepinfo.com](mailto:support@deepinfo.com).

Locked [Deep Search & Insights (DSI)](/guide/dsi/) search screens show sample data behind the lock. It is demo data, not your
organization's data.

On the **FEEDS** page, a feed outside your package says **This feed is not included in your package**,
and you can download only its sample data.

### What the Package Includes

| Area | What the package includes |
|---|---|
| External Attack Surface Management (EASM) | Every EASM screen |
| Cyber Threat Intelligence (CTI) | The CTI screens. Without CTI in the package, the CTI dashboard shows a lock screen |
| Dark Web Search | The page opens with either CTI or Dark Web Search in the package. Running a search needs Dark Web Search |
| Brand Risk Protection (BRP) | Every BRP screen |
| DSI | Each feature on its own: Domain Search, domain details, Vulnerability Search, vulnerability details, each type of instant lookup, the Feeds page and each feed |
| Reports and Notifications | Both at once: the same package item includes the two |

### Other Things That Change What You See

- **An access error.** If a screen asks for data outside your package, a message appears at the bottom
  right: "There was a problem with your access permissions. Please get in touch with us."
- **An empty EASM inventory.** This is not a package lock: if your organization has no assets yet, every
  EASM page takes you to the page for adding assets first. See [Add assets](/guide/easm/add-assets/).

## Roles

The roles are **ADMIN** and **MEMBER**. There are no other roles and no custom permissions.

| What | Admin | Member |
|---|---|---|
| Your own settings: **Account Details**, **Security**, **Session**, **Notifications** | Yes | Yes |
| **API Keys**, **API Usage**, **API Logs** | Yes | Yes |
| The organization's **Settings** (name and logo), **Members** and **Security** (require 2FA) | Yes | No |
| **COMPANY SETTINGS** in the profile menu | Yes | No |
| Module screens: EASM, CTI, BRP, DSI, Reports, Notifications | Yes | Yes |

- Members do not see the admin-only items in the Settings sidebar. If a member opens one of those pages
  by its address, the platform shows **Account Details** instead.
- Both roles can use the module screens. When a member creates a notification rule or schedules a
  report, the member can choose only themselves as a recipient.
- On **API Keys**, the **TEAM MEMBER** column shows which member each key belongs to. Admins see the keys
  of every member. See [Create and manage API keys](/guide/settings/api-keys/).
- An admin changes a person's role on the **Members** tab with **SET AS ADMIN** or **SET AS MEMBER**. See
  [Manage members and invitations](/guide/settings/members/).

## Good to Know

- **Upgrades go through Deepinfo.** Use **TALK TO US** or **TALK WITH AN EXPERT** on a lock screen, or
  write to [support@deepinfo.com](mailto:support@deepinfo.com).
- **API keys have the same limits.** An API call to an endpoint outside your package returns
  **403 Forbidden**. See [Errors](/getting-started/errors/#403-endpoint-not-in-plan).

## Do This With the API

- [Authentication](/getting-started/authentication/): what a 401 and a 403 mean for an API key.
- [Errors](/getting-started/errors/): the full error responses.