Organisation and members
Organisations
Section titled “Organisations”Comcent is multi-tenant: one instance can host several organisations, each with its own members, numbers, trunks, queues and call history. Every organisation has a subdomain, which appears in URLs (/app/<subdomain>/…), in API paths (/api/v2/<subdomain>/…) and in members’ SIP addresses.
When you claim a self-hosted instance, the setup form creates the first organisation and makes you both the instance super-admin and an admin of that organisation.
To create another organisation, go to /org/create (also reachable from the organisation list at /org). You set:
- Organization Name (3–60 characters)
- Sub domain (3–15 characters, unique). It cannot be changed later.
- Sip username: your own username inside the new organisation.
| Role | Can do |
|---|---|
| ADMIN | Everything: SIP trunks, numbers and flows, queues, voice bots, members, call history, daily summaries and settings (webhooks, API keys, AI & Analysis). |
| MEMBER | Make and take calls, set their own presence, manage their own profile and API keys, and view and work with promises. |
Invite members
Section titled “Invite members”Sign-up is invite-only by default. On a self-hosted instance you can also let people with certain email domains register themselves with ALLOWED_SIGNUP_DOMAIN (see Configuration).
- Open Members and enter the person’s Email and Role, then click Invite.
- They receive an email (so SMTP must be configured) with a link to the invitation.
- They sign in or create an account, and choose a Desired username. This becomes their SIP username in the organisation.
Pending invitations are listed with their status and how often they were sent; use Resend to send one again. An organisation has a maximum number of members; when it is reached, the Members page tells you so.
Usernames
Section titled “Usernames”SIP usernames start with a letter, are 3–20 characters long, and may contain letters, digits, ., _ and +. A member’s SIP address is username@<subdomain>.<COMCENT_DOMAIN>.
Manage members
Section titled “Manage members”The Members table shows each member’s name, email, SIP username, SIP password, extension and role. Choose Edit to:
- Edit Role: switch between ADMIN and MEMBER.
- Regenerate password: issue a new random SIP password, for example if a desk phone’s credentials leaked.
Your profile
Section titled “Your profile”Open your profile (Members → me) to see your role and SIP address, choose your Default Outbound Number (the caller ID used when you do not pick one in the dialer), and create or delete your personal API Keys.
Presence
Section titled “Presence”Presence controls whether queues offer calls to a member.
| Status | Set by | Meaning |
|---|---|---|
| Available | Member | Ready to receive queue calls. |
| On Break | Member | Temporarily away; no queue calls. |
| Logged Out | Member or system | Not working. Set automatically when the member’s phone or browser unregisters, or when they miss too many queue calls in a row. |
| Reserved | System | A queue call is ringing for this member. |
| On Call | System | On a call. |
| Wrap Up | System | After-call time, set by the queue’s wrap-up setting. |
| Busy | System | The member rejected a queue call; they are paused for the queue’s reject delay. |
Members change their status from the dialer. Admins can watch everyone’s status live on the Presence page and the dashboard (see Live calls and dashboard).
Sign-in options
Section titled “Sign-in options”Members sign in with email and password. Email addresses must be verified before the first password sign-in; the verification link is valid for 24 hours, and a forgotten password can be reset with a link valid for one hour.
Self-hosted instances can also offer single sign-on through any OpenID Connect provider, or turn password sign-in off. See Configuration.