> For the complete documentation index, see [llms.txt](https://docs.cyberawaresecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cyberawaresecurity.com/admin-portal/recipients/creating-recipients.md). # Creating Recipients In this article, we guide you through the process of creating Recipients within the platform. Recipients are employees who have access to the learning portal. You'll learn how to add new Recipients and ensure they are properly enrolled in the relevant Training Campaigns {% embed url="" %} **1.** Let’s create a **new** recipient. To do that, navigate through the **Add Recipient** option:

You will be prompted with the following pop up:

**2.** Let’s add the details for this example:

**3.** We clicked on **Save** and we were prompted with a confirmation window. Click **OK** to proceed.

**4.** The user has been created as expected! ![](/files/MYe7lrWsvKZNjWPkxzhZ) **5.** Like earlier, this is an alternative place where you can **archive** your users. Click on the **trash can** symbol to proceed. ![](/files/P8G2wABFE337pEidSAI7) **6.** Go ahead and tap on **Archive:**

**7.** On the last pop up, click on **OK.**

![](/files/bviQA5u91w546opGRVUz) **8.** Navigate to **Archived Recipients** to confirm the change:

**9.** To reactivate this user, click on the button shown in the following image:

**10.** When the prompt pops up, **Restore** the user:

**11.** Click **OK** to finalise:

**12.** The user is now restored!

**13.** When navigating to the **Recipients** section of the portal, we get the following output. Normally there wouldn’t be any recipients shown at the beginning, but we have created one for demonstration purposes.

**14.** You can view **more than 10 entries** in a single page by clicking on the indicated option of the following screenshot:

**15.** To view the recipient’s details, click on the **eye** button.

Before we continue with the rest, let’s summarise what is displayed on this specific user’s profile. **16.** The **Recipient Details** window is split up to **three** parts. The **first upper** part shows different details and options that compose the user’s profile in addition to the risk scores:

**17.** The **second,** or else, **middle** part shows various details and statistics in regard to the overall training of the user.

**18.** Moreover, you can **change** the **format view** for the courses. That would be from **Table** to **List** and vice versa.

**19.** The **last** part of the recipient’s details window shows us whether any data breach has occurred in regad to that user. The platform crawls through the dark web and composes the following structured report with all of the retrieved information. ![](/files/pvgWiz0BDJwa2bUc0IUo) **20.** If you want to go back to the Recipients default page, click **Go Back:**

**21.** On the left-hand side, we can see the **Groups** in which the recipient belongs to. You can click on any of the groups appearing, so you can view them:

**22.** You should receive a similar output: For further information regarding groups, click on this [link](https://docs.cyberawaresecurity.com/admin-portal/groups) so you can be redirected to the appropriate article.

--- # 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.cyberawaresecurity.com/admin-portal/recipients/creating-recipients.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.