Director

Director is the control plane for the Compositions family. It owns identity and sign-on, it owns users and groups, and it owns access — which means there is exactly one place where the question “who is this, and what may they reach?” is answered.

That matters more for AI than it does for ordinary software. A conventional application shows a user the screens they are entitled to. An agentic AI is asked for an outcome, and works out the path itself — so the boundary cannot live in the interface. It has to live in identity. Director puts it there.

Groups, not guesswork

Users belong to groups, and groups decide what an AI will do on their behalf: which capabilities they can reach, and how the assistant behaves for them. A group is whatever is useful to you — a team, a function, a plant, a project, a customer. It is not a Windows group and not borrowed from anywhere else; it is yours.

Every node accounted for

Components register themselves with Director and report in continuously. What is deployed, where, on what version, and whether it is alive right now — on one screen. An administrator approves a new node before it can be used, and can disable one at any time. That decision is enforced, centrally, rather than requested politely.

No back door

There is no second place a user might exist, and no component that can be reached around Director. If Director will not let someone in, they are not in.