Configuring Centriu
This section explains how to make Centriu reflect your company: structure, teams, permissions, integrations, and customizations that ensure the system fits your way of operating.
1Account structure
Organization data
- • Name, domains, language, currency.
- • Definition of business units (B2B, B2C, regions).
Teams and roles
- • Creating teams (Sales, CX, Ops).
- • Linking people and leaders.
- • Best practices to avoid duplicating teams.
Roles and permissions
The difference between admin, manager, and operational user.
Profile examples:
- CX Lead: Full access to dashboards and tickets.
- Sales Analyst: Access to the funnel, without access to global settings.
2Dictionaries and standards
Statuses and Categories
How to define opportunity statuses, ticket stages, and loss reasons. Use clear naming standards to keep reports clean.
Custom fields
Create new fields only when necessary (e.g., segment, contract size). Always try to reuse existing ones.
Models and templates
Standardize funnels, playbooks, and dashboards by duplicating approved templates across the entire company.
3Integrations and automations
Native
Connection to legacy CRM, email marketing, ads, and gateways. Understand what Centriu reads and sends.
API
A developer's overview of how to use the Centriu API, route naming, and token management.
Automations
Examples: High CAC alert, automatic task in Run if NPS drops, lead registration via bot.
4Configuration governance
- Strictly define who can create dictionaries.
- Document relevant changes.
- Test configurations in a controlled environment before releasing.
5. Recommended content in this group
- Complete guide to permissions and roles in Centriu OS
- How to structure teams and business units without overcomplicating
- Dictionaries and fields: how to keep your reports clean
- Integrations: a checklist before connecting any tool
Need technical support?
Questions about the API, complex integrations, or advanced settings?