> For the complete documentation index, see [llms.txt](https://docs.inopli.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inopli.com/drp/client-onboarding-and-configuration/company-setup.md).

# Company Setup

The activation of <mark style="color:green;">Inopli's Digital Risk Protection (DRP) module</mark> for a monitored entity begins with the configuration of its monitoring profile. This is a required first step before any data collection or threat detection can begin. The monitoring profile provides the baseline identity data and digital presence of the company, allowing the DRP system to contextualize and correlate findings accurately.

The process must be initiated by the authorized partner or designated contact for the monitored company. A formal monitoring activation request must be submitted, including a complete set of required profile information. Once validated, this data is used to guide and personalize all DRP monitoring tasks across surface web, social media, deep/dark web, and app ecosystems.

#### Required Information

The following fields must be provided when requesting DRP activation:

* `brand name` — Display name of the monitored brand
* `legal name` — Official registered name of the entity
* `tax id` — Legal tax identifier of the organization
* `country` — Country of registration or operations
* `language` — Primary language used in brand presence and communication

**Social & Digital Presence**

These informations are essential for monitoring across communication channels and public platforms:

* `facebook`, `instagram`, `twitter`, `linkedin`, `youtube`, `tiktok`, `threads`, `telegram`, `whatsapp`, `wechat`, `qq`, `reddit`, `snapchat`, `pinterest`, `tumblr`, `medium`, `vk`, `flickr`, `vimeo`, `stackoverflow`, `discord`
* `github`, `gitlab`, `google_play_id`&#x20;

#### Process Notes

* Once activated, the system begins entity correlation and enrichment tasks for threat detection.
* Any changes to this profile after activation must be submitted via the update workflow.


---

# 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.inopli.com/drp/client-onboarding-and-configuration/company-setup.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.