staff roles and access in a network of locations: who sees what
A shared password for the shift, logins in a chat and a dismissed administrator who can still sign in. How to put access in order across a network of locations.
id.knopka
ID.Knopka — one staff account, roles by location and a shared directory
an employee has one account for all knopka products — CRM, ERP and LMS — and their own role at each location. sign-in with a code from SMS or a password, invitation by link, and locations and cities are set up once — for all products.
id.knopka · one sign-in for all products
what it gives you
what ID.Knopka gives you
01
one staff account
one account for all knopka products — CRM, ERP and LMS — without a separate login for each system. sign-in with a code from SMS or a password.
02
roles by location
one person can have different roles at different locations: location manager at one, administrator at another. at each location they see what their role allows.
03
invitation by link
the manager sends the employee a link — the employee registers and lands in their location with the right role. no calls to support.
04
a shared directory
locations, cities, time zones and currencies are set up once, and all products take them from there. for a network in several countries this is the foundation, not a setting for “later”.
how it works
access that you set up once
sign-in
from invitation to work — three steps
the location manager sends a link, the employee signs in with a code from SMS or a password — and right away sees their locations and what their role allows, in all products.
- invitation — the manager sends a link
- sign-in — with a code from SMS or a password
- work — in the CRM, ERP and LMS you see your own locations and your own role
in practice
one person — three locations — one account
Marina: Shchyolkovo — location manager, Korolyov — administrator, Mytishchi — administrator. one account, one sign-in, and a different role at each location.
- network employees and their roles by location
- invitation by link with the right role
- activity log: who changed what
products
where the account leads
who it's for
ID.Knopka for your niche
questions
frequently asked questions
how does an employee sign in?
with a code from an SMS to their phone number, or with a password. one sign-in opens all knopka products — CRM, ERP and LMS.
what if an employee works at two locations?
they have one account and their own role at each location.
how do I add a new employee?
the manager sends an invitation link. the employee registers through it and lands straight in their location with the right role.
why a shared directory of locations?
so that locations, cities, time zones and currencies are the same in all products. a location's time zone determines which day an order belongs to — if the directories diverge, the reports diverge too.
does the LMS also sign in through ID?
yes. an employee signs in to the LMS with the same account as in the CRM and ERP.
can I see who changed what?
yes, the ID dashboard has an activity log.
can ID be bought separately?
ID is the foundation for the other knopka products: sign-in and the directory. it is included in any set of products.
blog
from the blog
migrating from another CRM: not an export and an import, but a check of every number
A discount applied to the wrong unit, a lost time zone and technicians from thirteen locations at once — three places where a migration from an old CRM diverges from reality.
CRM, ERP and LMS: when to take them separately and when together
When one product is enough, when you need two, and when everything together — and how to connect the CRM, ERP and LMS so that data isn't lost at the joints.
request
we'll show you how access works in a live network
send a request — we'll show you sign-in, roles by location and the directory and suggest where to start.