Permissions in IZI CRM — what they are
Permissions in IZI CRM — what they are
Section titled “Permissions in IZI CRM — what they are”A permission is a single right to perform one specific action in IZI CRM — for example, “process a cash collection,” “view the KPI dashboard,” or “cancel a player’s tariff.” Permissions are never granted to a staff member directly. Instead, they are assembled into a role — a named bundle of rights — and that role is assigned to the person. You manage permissions inside Organization → Roles. For a step-by-step walkthrough, see how to configure roles and permissions in IZI.
Permissions operate at two levels: club-level (scoped to the specific clubs chosen when the role is assigned) and organization-level (apply across the entire network).
Club permissions
Section titled “Club permissions”| Group | What it covers |
|---|---|
| Club administration | Core floor access — orders, bar, clients, shifts; equipment; IZI Boot; screensavers; monitoring; warehouse; order cancellation and restoration |
| Club settings | Tariff and product catalog, schedule, equipment configuration |
| Analytics | KPI, daily reports, bar analytics, tariffs, bonuses, sessions, clients, shifts, suspicious operations, promo codes, price simulator |
| Financial operations | Cash registers, gaming and bonus balance adjustments, refunds, cash collection, inter-account transfers, discount application |
Organization permissions
Section titled “Organization permissions”Apply across the entire network regardless of which club the staff member works in.
| Permission | What it grants |
|---|---|
| Integrations | Manage payment providers and payment methods |
| Player groups | Create and edit player groups |
| Transaction tags | Manage the tag reference for operations |
| Campaigns | Marketing campaigns |
| Promo codes and campaigns | Create and manage promo codes |
User and role management and creating new clubs are only available with the Full Access flag enabled — expanding the network and controlling who has access should be reserved for the owner or someone they explicitly trust.
Permission dependencies
Section titled “Permission dependencies”Some permissions automatically enable dependent ones: most club permissions require Basic Access; Catalog activates Schedule and Equipment; Campaigns activates Player groups. If IZI detects a mismatch on save, it shows “Rights will be normalized” — expected behavior, not an error.
Related terms and guides
Section titled “Related terms and guides”- Role in IZI — a named set of permissions assigned to a staff member
- How to configure roles and permissions in IZI — step-by-step guide with example configurations
- IZI CRM access permissions reference — full list of toggles and what they do
- Roles in IZI: owner, Administrator, and custom roles — how the role model works
Frequently asked questions
What is a permission in IZI?
A permission is a single right to perform one specific action in the CRM — open a shift, view KPI, process a cash collection. Permissions are never assigned to a staff member directly; they are assembled into a role, and that role is then assigned to the person.
What is the difference between a permission and a role?
A role is a named collection of permissions. A permission is one item inside that collection. IZI ships with one built-in staff role — Administrator. For any other profile (for example, a cashier or a floor manager), the owner creates a custom role, gives it a name, and picks exactly the permissions that profile needs.
What levels do permissions operate at in IZI?
Permissions are split into two levels: club-level (apply only to the specific clubs selected when the role is assigned) and organization-level (apply across the entire network — integrations, campaigns, promo codes, player groups).
What does Full Access mean in the context of permissions?
The Full Access flag on a role automatically enables every permission: club-level, organization-level, and system-level (user management, creating new clubs). You do not need to tick individual items when this flag is on.