Skip to content

See your organisation's scopes

Documented Checked against the CLI's current help and source. Not run end to end. CLI 0.4.0, checked 2026-11-05.

See your organisation's scopes

List every scope in your organisation and the path that holds work to each one.

What you get: the shape of your organisation as Quox sees it, from the whole org down to each team, with the path that scopes work and permissions to the right level. You need: QuoxCORE. About 2 minutes.

scopes
quox scope listID                            Name                          Type        Path                                                            Depth (0=org,1=div,2=dept,3=team)01K50FSL8KNRWV1HKEJYW4JM07    Demo User's Workspace         org         /org/01M50FWN7T8XG9K9P9JN0TA5WF                                 001K6KE8LPID9V5KT06SXS6ZBST    Field engineering             division    /org/01M50FWN7T8XG9K9P9JN0TA5WF/division/01M6ME8NSHK200ZJ...    101K6KD7CN9J7MX3R89NVP64B6W    Field operations              division    /org/01M50FWN7T8XG9K9P9JN0TA5WF/division/01M6MD7CQ578T2CE...    101K50FSLAM0XTPWT3DEP0AQAVW    Demo User's Workspace Team    team        /org/01M50FWN7T8XG9K9P9JN0TA5WF/team/01K50FSLA28AANT00AC6...    3
From a real run on the demo profile. Long paths shortened by the CLI.

Each row is one scope. The Type column tells you its level, and the Depth column numbers that level, from 0 for the whole organisation to 3 for a single team. The Path column is what Quox uses to hold a piece of work, a credential or a permission to one part of the business.

The command only read the scope tree. It changed nothing and raised no approval. Every scope sits under the organisation at the top, and the path shows exactly where it hangs, so you can see which division or team a scoped item belongs to.

Create a division or a team (see Set up divisions and teams), then run quox scope list again. The new scope appears with its own path and depth.