Docs / Account / Organization and team tree
Organization and team tree
An organization is one customer of Token Controller: its people, teams, projects and periods. Its people sit in the team tree.
Browse the docs
Getting started
Attribute
Account
Reference
Organization settings
| Setting | What it does |
|---|---|
| Cost source | How your provider charges you. It decides what the close reconciles against; see Bills. |
| Attribution target | The share of cost you aim to place on tickets and projects. Default 80 percent. |
| Approval | On or off. See Approval. |
| Sign-in | Which sign-in providers members may use, and which email domains. |
The team tree
People are arranged as person, team, department, organization, following your org chart. A department is usually a discipline such as engineering, design or QA. Each person belongs to one team at a time. Every node is a cost center, so a team's cost is the sum of its people's.
The team tree is separate from projects on purpose: one person can work on several projects but belongs to one team.
When someone moves
When a person changes team or leaves, only future token entries follow. Past postings keep the team they had, so last month's reports do not change.
Last updated 8 October 2026 · Edit this page
© 2026 Jan Beck · Privacy · Imprint