An instance is an independent PostgreSQL database on a specific host.
- It has its own versioned structure and migration lifecycle.
- Most runtime configuration is handled on the host via Node Manager.
- User assignment and selected administrative operations are managed from DBM.
Each instance stores system settings such as version, size, limits, and default permissions.
- Browse and open projects.
- Work with roles, groups, devices, and API keys.
- Configure project-level and lower-level access (if authorized).
- Manage objects and data according to permissions.
- View and design object structures only when Architect permission is granted.
Instance-level user permissions extend project-level permissions.
- All projects access: grants effective access to all projects when project authorization is evaluated.
- Group organizer: allows creating groups.
User-specific administrative permissions inherited from lower hierarchy:
- Role moderator: role and user moderation tasks in instance scope.
- Admin: advanced instance administration (projects, history, deleted entities visibility, etc.).
Instance defines separate default permissions for:
- user individuals
- device individuals
Important behavior:
- For users, authorization combines role-derived permissions plus instance defaults.
- For devices, instance-level permission bits are not assigned directly; devices are already inside the instance context and rely on project/table/object authorization.
- Instance access is evaluated first.
- Project access is evaluated next.
- Object structure permissions are applied.
- Object-specific permissions are applied when object authentication is enabled.
For full details and inherited scopes, see:
Use this set when working inside one instance:
Instance permission checks are inherited into project-level checks where applicable.