Administration > Roles > Database roles

In addition to the roles in dpSpatial, there are also a number of roles in the database that entitle dpSpatial to connect and read / modify data. These roles are called database roles and are only used internally by the system (they do not need to be maintained by the administrator or assigned to any user).

Database roles	Function
FPPREAD	Database role for users who should only have read permission
FPPWRITE	Database role for users who have both read rights and write rights (on any object). Also contains FPPREAD
FPPADMIN	Database role for users who have any administrative rights in dpSpatial. Also contains FPPWRITE
BIOS_USER	Database role held by FPPREAD, FPPWRITE and FPPADMIN. Mainly provide read rights on tables in the BIOS schedule
COMPONENT_OWNER	Database role for schema owners such as FPP, PIPING, FPDH
CONNECT	Default role in database that entitles you to connect to the database at all. Shared to FPPREAD automatically upon installation
TRACE_ROLE	Database role that entitles you to run tracking features in the database. Held by FPPREAD

Note. Previously, all roles in dpSpatial were managed as database roles. There may therefore be more roles than listed here, these have no function in dpSpatial. In addition, there are a number of default roles for each database (Oracle / PostgreSQL). For a description of these, we refer to the database owner's own documentation.