Beta verzia novej dokumentácie.

Impact of permissions on licences

In CDESK, account licences are not assigned manually; they are determined automatically based on the account’s authorised permissions. The permission settings therefore directly affect the range of the environment’s licence.

Licence permissions

The basic licensing model is based on the principle that even an account without a paid licence can read data. Users can therefore view records across modules without affecting their licence level. Charges only apply when an account has authorization to create, edit or delete data within a given module.

This leads to a practical rule: if you only need to grant someone access to view data, the licence range remains unchanged. Expenses are incurred only when that person is required to work within the module.

Selection of licence authorizations

In the permissions list, these permissions are marked with icons highlighted in yellow. Only the icons for write (), create () and delete () are highlighted – the icon for read access is not highlighted, as reading does not alter the licence. The same three icons are also shown in the legend in the Permissions column header.

You can get a quick overview of all such permissions using the All licence permissions filter above the list. You can use this when checking the environment if you need to find out exactly which licence an account is using.

Figure: Filter for all licence permissions

Note: The licence authorizations and the corresponding filter are only viewed in environments with the current licence model.

Conditions for including a module in the licence

The entire module is counted towards the licence as soon as at least one authorization selected in this way is enabled within it. If more than one is enabled, the licence impact does not increase further – the distinction is between ‘none’ and ‘at least one’. Permissions relating exclusively to data visibility are not included in the calculation.

Tip: If you need to reduce the range of your licence, simply removing one authorization from the module is not enough. The module will only cease to count towards the licence once none of the highlighted authorizations are enabled within it.

You can find detailed information about individual licences, their range and management options in a separate article on licences.