About Security Management
SpeedBase has two layers of security management.
Specify Default Access Permissions For All Information Objects
On the first layer, users are grouped into several security roles (i.e. user groups)
and every role has its own set of permissions where you may easily control
read/write permissions on database level.
For each group of users which work in the same team/department, a different security role
(such as 'support team', 'trainee' etc.) is created, so they share the same permissions when
accessing various information in your database.
So simply assigning an existing security role to a new user is sufficient to apply previously
defined access rights to him/her.
See User Groups for more info.
Create Access Right Exceptions For Catalogs / Fields / Users
In case you need a more detailed access control, you may define further access right exceptions
on the second layer, which overwrite the default permissions inherited from the first layer.
See Advanced Access Rights Manager for more info.
SpeedBase has the following security control features:
- Controlling detailed permissions for records like displaying, updating, activating, exporting etc...
- Applying default access permissions in usergroup level
- Applying extended access rights for the owners of records
- Creating access right exceptions for the selected user
- Creating access right exceptions for the selected catalog
- Creating access right exceptions for the selected field
- Enabling/disabling access right definitions
For default installation, SpeedBase uses its integrated (local) database. Your database is never accessible from the internet and all your data is saved on your own
local computer/network. That means, your database is as safe as any other file on your desktop against any malicious internet user.
For multiuser (Teamwork) license:
Beware that, access rights management is designed mostly for preventing accidental data loss, to keep the desired part of the information away
from curious people around and from your own users who simply do not need it. This feature shouldn't be considered as a high level of protection
against your own users. Do not consider it as a way to hide sensitive information from your own users.