Organize your company
As you add people, skills, and knowledge, you need a way to decide who shares what. OpenCrane does this with scopes.
What's a scope?
A scope is the reach of something — how widely it's shared. There are four, from narrowest to widest:
personal ▸ project ▸ department ▸ org
(one person) (a team) (a division) (everyone)Departments and projects aren't folders
This is the key idea: you don't create a department as an object. There's no "new department" button. Instead, a department (or project) is simply a label you attach to people, skills, and knowledge. OpenCrane uses those labels to decide what's shared and with whom.
That keeps things flexible — your org structure lives in the labels you choose, not in a rigid hierarchy you have to maintain.
Personal scope is your assistant's scope
Personal isn't just the narrowest option on the list — it's the scope your personal assistant always operates in. A managed agent, by contrast, is created at project, department or org scope on purpose, because it's meant to be shared. See the personal/managed distinction.
How scopes show up
The same four scopes appear everywhere you share or restrict something:
- Skills are published at a scope and promoted to wider ones — a skill that starts personal can be promoted to project, then department, then org. → Agent skills
- Knowledge is organized into datasets by scope, so a department's documents only reach that department. → Organizational knowledge
- Access grants allow or deny something for a person, team, or whole department. → Control access
Grouping people
When you create an agent service, you can tag its team scope — see Create your first agent. That team label is what you then reference when you share skills with "engineering" or give a department access to a tool — so everyone in that group is covered at once.
A simple way to start
- Decide your departments (e.g. Engineering, Sales, Support).
- Assign each agent service and subject to the scopes it should use.
- Share company-wide skills and knowledge at org scope; keep team-specific things at department or project scope.
You can always widen a scope later — start narrow, promote as things prove useful.