Setting Up Access Levels in a SQL Database


 

  
 Applies To 
  
 Product(s):gINT Professional Plus
 Version(s):N/A
 Environment: Microsoft SQL Server
 Area: Data Entry
 Subarea: 
 Original Authors:

Dave Anderson, Bentley Software;
Kathleen Holcomb, Bentley Technical Support Group

  

 

We wish to limit what some users can do in our gINT SQL enterprise database.  For example, some users should be able to view data and output reports, but not change the data.  Other users should be able to edit data but not modify the database.

Introduction

Microsoft SQL Server allows you to control what kind of access you give to users.  

You can use either Windows or SQL Server authentication. Our example server uses Windows authentication.

In this example, we will establish 3 levels of user permissions:

Steps to Accomplish

Connect to the SQL database

  1. Connect to a SQL Server instance: 

  2. Navigate to Security Logins:

  3. Create or Select a User.

  4. Right-click on a user and select New Login…

  5. Right-click on a user and select Properties.

Administrative User: 

  1. Select Server Roles.  Check public and sysadmin.

  2. User Mapping: not necessary to select anything given the sysadmin authority.

Read-Write User:

  1. Select Server Roles.  Check public.

  2. Select User Mapping. Check the databases that the user can access.  Check the roles db_datareader, db_datawriter and public:

 Read-Only User (qa3): 

  1. Select Server Roles.  Check public.
  2. Select User Mapping. Check the databases that the user can access.  Check the roles db_datareader and public.

See Also

gINT V8i Enterprise User Guide: docs.bentley.com/.../gINT_enterpriseuserguide_v8_30.exe