Profiles

A profile is the link between people and skills. It groups a set of skills and a pair of execution permissions, and it's assigned to users. The set of skills a person sees in the chat is the union of the skills from the profiles assigned to them.

With no profile, the chat opens empty

A user with no profile assigned — administrators included — sees no skills in the session. This is the most common source of confusion: after creating a user, remember to assign them to a profile. See the notice on the Dashboard.

The profile list

The Profiles page (/org/profiles) lists the organization's profiles. Each row shows the name and description and leads to the detail view. From the list you create new profiles and open existing ones to edit.

Create a profile

Use Create profile and provide:

1. Name — identifies the profile (for example, Sales Team, Engineering, Finance).
2. Description — a sentence about the profile's purpose.

The profile starts empty: you add skills and users in the detail view.

Profile detail

The detail view brings together editing and the two association cards.

Edit

Field	What it does
Name	The profile's display name.
Description	Explanatory text.
Allow local skill execution	Whether this profile's skills can execute code locally on the user's machine.
Allow writes outside workspace	Whether the agent can write outside the workspace for anyone with this profile.

How profile permissions combine

Allow local skill execution and Allow writes outside workspace are one of the layers of the policy, which follows deny-wins. A profile can only restrict the baseline — never expand beyond what the platform and the organization permit. Remember that the per-user overrides (in Users & roles) also take part in this combination.

Users

The Users card shows who is assigned to the profile:

• Add — assigns an existing organization user to the profile.
• Remove — removes the assignment (on the next policy calculation, the person loses the skills exclusive to this profile).

Since the skill view is the union of profiles, a person can be in more than one profile and combine capabilities.

Skills

The Skills card defines the profile's set of capabilities:

• Add — includes a skill from the organization's catalog.
• Remove — removes the skill from the profile.

Skills only appear once published

A skill can only join a profile after it exists in the organization's catalog (created or imported and published). See Skills (governance) and skill authoring.

When changes take effect

Changes to profiles (adding/removing skills or users, changing permissions) recompute the organization's effective policy. Clients receive the new policy on the next request and sync the skills at the start of the session — installing what gained access and removing what lost it. In an already-open session, ask the user to start a new session if the change doesn't reflect immediately.

See also

👥Users & roles

Create people and adjust execution overrides.

Open →🧠Skills (governance)

The catalog the profile's skills come from.

Open →🏢Organizations & policies

The mental model behind profiles and policies.

Open →