> For the complete documentation index, see [llms.txt](https://docs.pascom.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pascom.net/en/setup/user/client-profiles.md).

# Manage server side app profiles for users

In this tutorial you will learn how to manage app profiles on the server side.

## Concept

App profiles allow you to customize the PASCOM app to your way of working. Each user can create and manage their own profiles in the PASCOM app. At the same time, server-side app profiles can be defined for all users. How the administration of server-side app profiles works is explained in the following sections.

{% hint style="info" %}
In order for users to use the app profiles and set up their own profiles, the **profile.personal** user role is required.
{% endhint %}

## Overview

The server-side app profiles can be found under **Users** > **Profiles**. Here, by **default**, 2 global app profiles are already set up. The profile **"Available"** and **"DND"**. You can use these profiles but also set up your own profiles. In the field **"Assignment"** you can see that these are **System profiles**.

![Client Profile overview](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-fb57126cc4cf633ebe3b320dd2f7cfe13b80ec8d%2Fprofiles-overview.en.png?alt=media)

**What do these 2 profiles do?**

The **"Available"** profile activates all endpoints assigned to the user. The **"DND"** profile deactivates all endpoints assigned to the user. Thus, by default, there are 2 global profiles that control reachability.

## Set up app profiles on the server side

#### Base Settings

Click **Add** in the overview of the profiles. In the upper area set the basic settings of the profile.

![Client Profile Base Settings](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-78f49d30c498f015a07453d2a44d7d6d5224a7b3%2Fprofiles-basesettings.en.png?alt=media)

| Setting         | Description                                                                      |
| --------------- | -------------------------------------------------------------------------------- |
| Profile Name    | Name of the profile                                                              |
| Color           | Color of the icon used                                                           |
| Icon            | The icon visualizes the profile in the presence status                           |
| Icon visibility | Enable / disable the visibility of the profile icon                              |
| Sticky Profile  | Enable / Disable - This allows the profile **not** to be overridden by triggers. |
| Roles           | Activates the profile for a role. By default the role **"All "**                 |

#### Set a trigger

With triggers you can define whether the profile should be activated / deactivated automatically. Triggers can control your profile fully automatically.

#### Trigger - Timing

With the time control you can set a time automation of the app profile.

![Client Profile Trigger - Timed](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-652cd635fe4fae424dad9529544f639801e9d266%2Fprofiles-trigger-time.en.png?alt=media)

In the **Time** item, you specify a **time** at which the profile is triggered. In addition, you can also set up a **repeat** on certain weekdays, for example.

#### Trigger - Microsoft Teams Meeting

The **Microsoft Teams Meeting Trigger** automatically detects when you start a phone call or video conference via **Microsoft Teams** and then switches to a profile e.g. **Teams Meeting**.

The synchronization usually takes between **05 and 10 seconds** until the presence status in the PASCOM app switches.

{% hint style="info" %}
You should **pin** (sticky profile) a **profile** with the **Mircosoft Teams Meeting trigger** so that it cannot be automatically overridden by other profiles during a Teams meeting.
{% endhint %}

After a **Teams meeting**, the presence status automatically jumps back to the previously used profile.

![MS Teams Trigger](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-87dbfc121510207098fba45b9fb8be4fdb0020f6%2Fclientprofiles-msteamstrigger.en.png?alt=media)

#### Set up actions

Actions are the elementary building blocks of app profiles. Here you define how the PASCOM app should behave when changing profiles. A distinction is made between actions that are triggered when **entering / activating** and when **leaving / deactivating**.

{% hint style="success" %}
Think about what you want to achieve with the server-side app profile so that profile changes are coherent and make sense to your users.
{% endhint %}

![Client Profile Actions](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-e238137a5651626aa361c60cc811572ce3053f83%2Fprofiles-actions.en.png?alt=media)

| Aktion                   | Beschreibung                          |
| ------------------------ | ------------------------------------- |
| Change FollowMe Settings | Changes the device setting of a user  |
| Set GSM Mode             | Activates / Deactivates the GSM Mode  |
| Team Login               | Logs the user into a team             |
| Team Logout              | Logs the user out of a team           |
| Team Pause               | Pauses a user in a team               |
| Team Unpause             | Cancels the pause of a user in a team |
| Set Workplace            | Sets a workplace to the user          |
| Unset Workplace          | Removes a workplace from the user     |
| Set redirect number      | Sets a redirection                    |
| Unset redirection        | Cancels a redirection                 |

#### Chain actions

The real strength of an app profile lies in the chaining of actions. You can chain multiple actions in a profile according to your preferences, making the app profile a powerful UC tool. The following applies here: **Actions are processed chronologically from top to bottom.** You can chain as many actions together as you need.

![Client Profile Actionchain](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-d280fbf5e4bf951e383ee85ab656020b4dd536cd%2Fprofiles-actionchain.en.png?alt=media)

Of course, action chains work when entering and leaving a profile.

#### Save and provide actions

After clicking **Save** you will find your new profile in the profile overview. By the **"Assignment"** you can see that it is a profile from an **Admin**. The server-side app profiles are directly available after **saving** and can be used.

![Client Profile saved](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-7e6a685f392677409f1ce9b555f004b4783be205%2Fprofiles-saved.en.png?alt=media)

## Delete app profiles on server side

You can easily delete server-side app profiles. **Highlight** your app profile and click **Delete**.

![Client Profile löschen](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-d79468930d19197bb5b3f07ff99f0a5efe0ff11c%2Fprofiles-remove.en.png?alt=media)

{% hint style="warning" %}
The 2 server-side profiles, which are present by **default**, cannot be removed / deleted.
{% endhint %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pascom.net/en/setup/user/client-profiles.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 `build a script that syncs our docs to a CMS` 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.