Docs/Administration/Teams

Teams

Group workspace members into named, colored teams with a focus area and pinned reveals so Orion delivers a focused briefing per team.

WeaverLuminaryUpdated June 2026 · 6 min read

✦

In this section

Part of Celiq's semantic layer platform. Connect your warehouse, model your data once, query it everywhere.

💡

Tip

What it is — A way to group the people in your workspace into named, colored teams, each with an optional focus area and a set of pinned briefing reveals.
When to use it — When different groups (Growth, Finance, Supply Chain) care about different parts of the data and you want Orion to tailor each group's briefing.
Where to find it — Lumen → People → Teams.
Who can use it — Weaver and Luminary can create, edit, delete teams and assign members. Tracer and Lens can see the list but not change it.

A team in Celiq is not a chat channel and not a permission level. It is a labelled bucket of members that carries two pieces of guidance for Orion: a focus area (a short phrase that steers the narrative) and a list of pinned reveals (the Discover reveals Orion should prioritise when it writes that team's briefing). When a member belongs to a team, their daily briefing is generated once for the whole team — which is cheaper to run and more relevant than a generic, one-size-fits-all briefing.

Overview

The Teams page has two parts. At the top is a grid of team cards, each showing the team's color dot, name, member count, focus area, and a preview of its pinned reveals. Below that is a Members table listing every user in the workspace with their name, email, role, and current team assignment.

Two roles are at play here, and they are independent:

Role (Luminary / Weaver / Tracer / Lens) controls what a person is allowed to do in the workspace. You manage that on Users.
Team controls how Orion tailors that person's briefing. You manage that here.

A person can be a Tracer on the Finance team, or a Weaver on the Growth team — role and team are set separately and do not affect each other.

When to use it

Create teams when:

Different groups want their daily and weekly briefings focused on different metrics — for example, Growth on acquisition, Finance on margin, Supply Chain on logistics.
You want to cut down the cost and noise of Orion briefings by generating one focused briefing per group instead of one broad briefing for everyone.
You want a quick visual grouping (the color dot and label) of who sits where, surfaced in the Members table.

You do not need Teams to control access — that is what roles and data security do. And Teams has nothing to do with sending messages to Microsoft Teams or Slack; see the note under Concepts.

Concepts

Term	What it means
Team	A named, colored group of workspace members, stored per workspace. Has a name, a color, an optional focus area, and a list of pinned briefing reveals.
Focus area	A short free-text phrase (for example "customer acquisition" or "margin & cost") that guides Orion's narrative for everyone on the team. Optional.
Color	One of eight preset swatches used to tag the team visually on the cards and in the Members table.
Pinned reveals (Default Discover reveals)	The Discover reveals Orion focuses on when generating this team's briefing. The picker lists every reveal defined across your domains. These become the defaults for team members who have not set their own personal pins.
Member assignment	Linking a user to one team (or none). A user belongs to at most one team at a time.

⚠️

Warning

Teams here is not the Microsoft Teams integration, and not chat. This page groups members and tailors Orion briefings. Sending messages out to Microsoft Teams or Slack is a separate, unrelated feature handled elsewhere in Celiq. Creating a team on this page does not create or connect any chat channel.

Getting started

Prerequisites:

You are signed in as a Weaver or Luminary to create, edit, delete, or assign. Tracers and Lens users can open the page and view it, but the create and assign actions are restricted.
Your workspace has members to assign. New members appear automatically in the Members table once they exist on Users.
For pinned reveals to be useful, your domains should define reveals. If no reveals exist yet, the reveal picker is simply hidden — you can still create the team and add reveals later.

To open it, go to Lumen → People → Teams.

Step-by-step

Open the Teams page

From the Lumen administration area, choose People, then Teams. You will see the team cards grid (or an empty-state prompt if no teams exist yet) and the Members table below.

Create a team

Click + New Team in the top right. In the dialog, enter a Name (required, for example Growth, Finance, or Supply Chain). The team will not save without a name.

Set a focus area (optional)

Type a short phrase into Focus area — for example "customer acquisition" or "logistics performance". This guides Orion's narrative for everyone on the team. Leave it blank if you do not want to steer the narrative.

Pick a color

Choose one of the eight color swatches. The selected swatch is outlined. The color appears on the team card and next to each member's name in the table.

Pin default reveals (optional)

If your domains define reveals, a Default Discover reveals picker appears. Click a reveal chip to pin it (a check mark and highlight indicate it is pinned); click again to unpin. Orion will focus on these reveals when generating the team's briefing, and they become the defaults for members who have not set personal pins.

Save the team

Click Save Team. The new card appears in the grid. To change a team later, click Edit on its card and adjust any field.

Assign members

In the Members table, click Assign on a person's row. In the dialog, pick a team from the dropdown (or choose — Unassigned — to remove them from any team), then click Save. The person's Team column updates with the team's color dot and name.

Examples

Suppose you want a Finance team that gets a margin-focused briefing.

Click + New Team.
Name it Finance, set the focus area to margin & cost, and pick the amber swatch.
In the reveal picker, pin the reveals that matter for finance — for example Gross margin by category and Cost trend.
Save, then assign your finance analysts to the Finance team from the Members table.

Conceptually, the saved team looks like this:

json

{
  "name": "Finance",
  "color": "#F59E0B",
  "focus": "margin & cost",
  "briefing_reveals": [
    { "domain": "orders",  "reveal": "gross_margin_by_category", "label": "Gross margin by category" },
    { "domain": "finance", "reveal": "cost_trend",               "label": "Cost trend" }
  ]
}

From then on, Orion uses the focus phrase to steer the narrative and treats briefing_reveals as the default reveals for any Finance member who has not pinned their own. Members can still override these in their personal briefing preferences; the team's pins act as the starting point. See Weekly briefings for how briefings are produced.

Best practices

Keep the focus area short and concrete. A tight phrase like "logistics performance" steers Orion better than a long sentence.
Pin only the reveals that matter to the group. A focused handful keeps the briefing relevant; pinning everything dilutes it.
Use color consistently so the same team is recognisable at a glance across the cards and the Members table.
Set role and team separately. Decide a person's permissions on Users and their briefing focus here — they are different decisions.
Revisit teams as your domains evolve. When you add new reveals in your domains, update the relevant teams so their briefings include the new content.

Tips

💡

Tip

You do not have to pin reveals to get value. A team with just a name and a focus area already gives Orion enough to tailor the narrative. Add pinned reveals later once you know which ones the group reads most.

Common mistakes

⚠️