Adding, Editing and Deleting SQL User Information
You use SQL stored procedures to add, edit and delete users stored in the database. Note that you must have Administrative privileges to run these stored procedures.
The following three tables, listed here with their fields, store all information for the SQLUM:
CustomUM.User
- UserID
- UserName
- UserPassword
- PasswordHash
- UserDescription
- UserEmail
- ManagerID
- DisplayName
CustomUM.Group
- GroupID
- GroupName
- GroupDescription
CustomUM.UserGroup
- GroupID
- UserID
You may notice that the User table includes information about the user's manager. This is useful in cases where you need to assign tasks to the originator's manager, such as in a Leave Approval app, for the manger to action. Both the manager and the user need to have accounts in SQL. The users ManagerID field is the UserID field of his or her manager.
See the following topics for more information about SQLUM:
- Planning for SQL User Manager in K2: Overview and getting started with SQLUM
- Non-Active Directory / Workgroup Installation: Similar to a standard K2 installation, but SQLUM is the only User Manager available.
- Configuring a Secondary SmartForms Runtime Site: Configure a secondary SmartForms runtime site for SQL-based or anonymous users.
- Configure SmartForms for SQL Server User Manager (SQLUM): Detailed steps on configuring the issuer, claims, and realms for a primary or secondary SmartForms runtime site
- Configuring the SQL User Manager: Configuring SQLUM as a primary or secondary identity provider.