Administration
Organisations
Manage the core organisational configuration that defines how your Telblu environment is structured.
An Organisation is the highest-level object within Telblu. It acts as the container for departments, users, strategies, governance, reporting and platform configuration.
Organisation Configuration
Define the organisation profile, identity and authentication policy, default roles, and administrative preferences that apply across the tenant.
Platform Settings
Control platform-wide behaviour including session policy, data visibility defaults, feature availability and integration endpoints scoped to the organisation.
Organisation Structure
Establish the hierarchy of departments, teams and workspaces that belong to the organisation and inherit its configuration.
Administration
Manage users, invitations, role assignments, delegated administrators and organisation-scoped settings from a single administrative control surface.
Overview
An Organisation is the root container for all platform data. Every department, strategy, user, workspace and governance process belongs to a single organisation. Changes made at organisation level can influence how information is organised and managed across the platform.
What is an Organisation?
In Telblu, an organisation is the root tenant object. Every other object - users, roles, departments, workspaces and configuration - belongs to a single organisation and cannot be shared across organisation boundaries. Understanding the organisation as a container is the starting point for configuring the rest of the platform.
What is an Organisation?
An organisation is the root object in the Telblu data model. It represents a distinct tenant - typically a company, group or entity - that owns its own users, roles, departments and configuration. All other objects in Telblu exist inside an organisation and cannot be shared across organisation boundaries.
What settings are configured?
Organisation-level configuration includes the organisation profile, authentication and identity provider policy, default role assignments, department structure, and any organisation-wide preferences that govern how Telblu behaves for members of the tenant.
How does it affect the rest of the platform?
The organisation defines the scope for every request. Authenticated sessions are bound to an organisation, role assignments are evaluated within it, and data access is restricted to objects owned by it. Changing organisation-level settings affects all users, departments and workspaces inside the tenant.
What can administrators manage?
Organisation administrators manage users and invitations, role assignments, department structure, authentication policy, identity provider configuration and organisation profile. Administrative actions are recorded in the audit log where available and are always scoped to the organisation the administrator belongs to.
What is inherited by departments?
Departments inherit the organisation's authentication policy, identity provider configuration and default role model. They exist inside the organisation's scope and cannot override organisation-level security settings. Department-specific configuration refines - but never replaces - what the organisation defines.
The organisation is the root of every other configuration
InfoOrganisation Hierarchy
Every object in Telblu exists inside a single organisation and carries its organisational context through the hierarchy. The organisation sets the boundary for users, data, roles and reporting. departments and downstream objects inherit that context and cannot operate outside it.
Organisation
Root tenant entity
Departments
Functional groups that own execution
Strategies
Approved direction owned by departments
Objectives
Measurable outcomes derived from strategies
Initiatives
Programmes of work delivering objectives
KPIs
Quantitative measures attached to objectives
Risks
Strategic risks linked to objectives
Governance
Approvals, policies and oversight records
Executive Control Centre
Unified executive view of the whole hierarchy
Organisation
The root tenant. Every user, role and object belongs to exactly one organisation. Organisation-level settings define identity policy, reporting defaults and administrative boundaries.
Departments
Functional groups that own strategy, objectives and delivery. Departments inherit the organisation's authentication policy, identity provider and default roles. They cannot override organisation-level security settings.
Strategies, Objectives, Initiatives, KPIs, Risks and Governance
Downstream strategic and operational objects are created within a department's scope. They carry the organisation identifier and department identifier into every record, ensuring access decisions and reporting always resolve to the correct tenant context.
Executive Control Centre
Rolls up the entire hierarchy into a single executive view. Because every upstream object shares the same organisational context, the Executive Control Centre can aggregate, filter and scope information consistently across the tenant.
Organisation Settings
The following settings are configured at organisation level. They become the defaults for the tenant and are inherited by departments and workspaces unless explicitly refined within their own scope.
| Setting | Description | Example value |
|---|---|---|
| Organisation Name | Display name shown throughout the platform | Acme Software Ltd |
| Industry | Industry classification | Enterprise Software |
| Country | Primary operating country | United Kingdom |
| Time Zone | Default organisation timezone | UTC |
| Fiscal Year | Reporting calendar | January – December |
| Default Language | Platform language | English (UK) |
| Reporting Frequency | Monthly / Quarterly / Annual | Quarterly |
| Status | Active / Inactive | Active |
Settings are scoped to the organisation
InfoOrganisation Information
The organisation information panel displays the current configuration for an example tenant. Administrators review and update these values from the organisation settings page.
Acme Software Ltd
Organisation profile
Organisation Name
Acme Software Ltd
Industry
Enterprise Software
Country
United Kingdom
Time Zone
UTC
Fiscal Year
January – December
Reporting Cycle
Quarterly
Created
12 January 2026
Status
Active
What belongs to an Organisation?
Every object in Telblu is owned by an organisation. The cards below describe the core object types that live inside the organisation container and how they inherit its context.
Departments
Business functions managed within the organisation. Departments own strategy, objectives, delivery and reporting, and they inherit the organisation's authentication policy, identity provider and default role model.
- Engineering
- Finance
- Sales
- Operations
- Human Resources
Users
Every authenticated user belongs to an organisation. User accounts, role assignments and sessions are scoped to the organisation, and users cannot access data or workspaces outside their assigned tenant.
- Employees
- Department leaders
- Administrators
- Executive users
Strategies
Departmental and organisational strategies are stored within the organisation. Each strategy carries the organisation identifier so that objectives, initiatives and KPIs can be filtered and reported by tenant.
- Growth strategy
- Operational excellence
- Risk reduction
- Product roadmap
Governance
Approvals, reviews and executive oversight operate within organisational boundaries. Governance records are linked to the organisation so that audit trails and compliance reports remain scoped to the tenant.
- Approval workflows
- Review cycles
- Policy attestations
- Compliance records
AI Intelligence
AI analyses approved organisational data and produces organisation-specific insights. AI outputs are scoped to the organisation and reflect only the data the tenant has chosen to make available for analysis.
- Performance insights
- Risk summaries
- Governance recommendations
- Trend analysis
Organisation Administration
Organisation administrators are responsible for keeping the tenant configuration accurate and ready for users, departments and downstream modules. Typical administration activities include the following.
| Activity | Description |
|---|---|
| Updating organisation information | Maintain the organisation profile, industry classification, timezone and contact details so that reports and integrations reference the correct tenant context. |
| Managing organisational structure | Define or adjust departments and reporting lines to reflect how the organisation is organised. |
| Configuring reporting periods | Set fiscal year, reporting frequency and period boundaries so that dashboards and executive reports align with the organisation's calendar. |
| Maintaining department hierarchy | Create, update and deactivate departments as the organisation changes, ensuring each department remains within the correct tenant scope. |
| Reviewing organisation settings | Audit authentication policy, identity provider configuration, default roles and platform settings to confirm they still match the organisation's requirements. |
| Preparing the platform for new departments | Configure roles, workspaces and governance templates before new departments are onboarded so that new teams inherit the correct organisation context. |
Organisational Relationships
The organisation object links every major module in Telblu. Each module operates within the organisation's scope and uses the organisation identifier to filter data, enforce access controls and produce reports.
Organisation
Root tenant object
Departments
Functional groups and reporting lines
Users
Authenticated members of the tenant
Strategies
Strategic plans and objectives
Governance
Approvals, reviews and oversight
Administration
Configuration and user management
AI
Organisation-scoped intelligence
Executive Control Centre
Unified executive view
These modules are linked through the organisation object. A user session is bound to an organisation, departments exist inside it, strategies reference it, governance records are scoped by it, and the Executive Control Centre aggregates information across all of them. AI Intelligence uses the same organisation boundary to ensure insights are tenant-specific and do not leak across organisations.
Administrator Considerations
The following guidance helps administrators maintain a consistent and secure organisation configuration.
Configure the organisation before downstream objects
InfoKeep organisation information up to date
Best practiceChanges to organisation settings may have tenant-wide effects
Info