Manager - Getting started.

The starting point is groups. In the group are locks/lock groups. Add users (with policy) and when you publish the keys, the users have access to the locks in the group with a validity according to "their" policy. Since most people have the same policy, the policy is linked to the person from a template.

Your role as described here is to:

Create policy (validity of keys)
Create groups

We assume in this description that your supplier has set up a lock configuration and entered the locks that you have been delivered into the respective group. Having said that, the groups with the respective locks already exist. You can of course also be both a manager and an admin (see separate page).

Se video - Förvaltare på 3 min

Policy (validity) : Create your first policy. The policy is the validity of the key and is tied to the user. You can set a fixed end time or a duration with automatic extension. With automatic renewal, the user can renew the key at any time and thus receives an updated key that has a validity corresponding to the policy.

Example: A policy is valid for 24 hours. A user who renews his key at any time gets 24 hours of validity. Previously (Criotive) there were shared keys that had 24 hours validity from a certain time and with that users could renew their key when there were only 3 hours left on this key without understanding why it didn't work after 3 hours and 1 minute.

Group: Create your first groups. In the Groups menu, click "+ Add New"

Enter a name and click "Add".

Change the group's links to locks : Click on the group you want to edit the links for. Mark the locks you want to link or remove from the group with the Add and Remove buttons respectively . The locks in the right field are included in the group and the left field are available locks for coupling.

ATTENTION! Any change you make that affects someone's key will cause a yellow box to appear prompting you to publish the changes made. The field is included on all pages of the user interface so you don't miss publishing your changes when you're done. Without publication, the changes will not reach users. It also means that you can complete all changes before publishing. Keep in mind that there may be other administrators in at the same time and making changes, which also affects the information in your yellow field.

Done!

* The user can only have one RFID key per lock configuration. An organization can have several lock configurations, but it is unusual to need more than one configuration if you only have RFID locks. A lock configuration tells the lock how it should act. For example, which sector on the Mifare card it should read from. If you have a lot of lock groups, you may need to read more sectors and with that you need more lock configurations. Another example is that you have both RFID and Bluetooth locks in the organization and with that different keys are needed.