Omnisnia CRM Docs / Account & Organizations

Account & Organizations

Teams — group members and manage who can see what

This page covers your personal account: your profile, the organizations you belong to and how to switch between them, inviting other people (for administrators), the difference between administrators and members, and personal API keys for automating your own work.

Your profile

Your account is your identity in Omnisnia. It carries your name and email — the details you provided when you signed up or were invited — and it is what every record you create, every task assigned to you, and every action you take is attributed to.

Belonging to organizations

Every user belongs to one or more organizations (tenants). An organization is a self-contained workspace, and all of its data is isolated from every other organization — see tenant isolation .

  • When you register, you create and belong to a single organization.
  • You can be added to further organizations — for example if you work across several companies, or an administrator invites you into theirs.
  • You can view the organizations you belong to at any time.

Switching organizations

You always work within one organization at a time — your active organization. Everything you see and do applies to it.

  • If you belong to exactly one organization, Omnisnia selects it for you automatically; there is nothing to switch.
  • If you belong to several, you choose which one is active. Switching organizations changes the entire workspace to that organization’s data — its clients, deals, channels, and everything else — and your previous organization’s data is no longer in view until you switch back.

Roles: administrator and member

Within an organization, users have one of two roles:

  • Member — the default role. Members can read and write the CRM and collaboration data of the organizations they belong to: clients, leads, deals, tasks, documents, channels, and so on.
  • Administrator — everything a member can do, plus setup and governance. The first account registered on an instance is the administrator.

Administrator-only tasks include:

  • Inviting and managing users
  • Managing organizations
  • Managing plans and billing
  • Configuring the AI inference endpoint that powers Omni
  • Managing licensing
  • Creating web-to-lead capture tokens — see Leads

Members can view some of these administrative areas but cannot change them; attempting an administrator-only change is refused.

Inviting users (administrators)

Administrators grow the organization by inviting users. An invitation creates an account for the new person and adds them to the organization, so they can log in and start working. As an administrator, you choose the person’s details when you invite them. New users join as members unless made administrators.

Personal API keys

If you want to automate your own work — a script that creates records, a small integration, or a scheduled job — you can create a personal API key. An API key lets a program act in Omnisnia on your behalf without logging in interactively.

A few things to know:

  • An API key acts as you, within the one organization it was created in. It cannot reach other organizations, even ones you belong to.
  • An API key is never granted administrator rights, regardless of your own role. Administrative changes cannot be made with an API key.
  • You can create and revoke your own keys. Revoke a key as soon as it is no longer needed or if it may have been exposed.

Setting up and using API keys is a technical task. For the full details — how to create a key, how to send it, and the endpoints available — see the API Reference (published separately for developers).

← PreviousGetting Started