SysAdmin User Guide

As a SysAdmin you have some/all CRUD rights on users, user’s claims, and the attributes (certifications, interests, skills, & tags).

• You cannot create a user. The only way a user is created is by registering themselves.
• You cannot set a password. But you can delete a password for a user requiring them to reset it before logging back in.
• You cannot delete an attribute. You can merely mark it hidden so it cannot be used in the future.

Having SysAdmin claims gives you no claims on organizations or tasks. It is not a super or root user in that context.

Pages

All CRUD activity is performed from the page listing the relevant objects. You find the object(s) in the list and then cRUD them from the list. And the list has a New button (except for users) to Crud new objects.

• Users List of selected users.
• Claims List of selected users and their claims.

Claims

Each claim has a type and a value. The type is SysAdmin or one of Admin, Organizer, TrustedHost, or Host (collectively referred to as Manager). The Value is “*” for a wildcard (everything) or…

• For SysAdmin it is in the form “Users:Delete” where the Users/Claims/Attributes defines the object you have a claim on and the Create/Read/Update/Delete defines the action you can take. To give a user multiple SysAdmin rights, give them multiple claims.
• For Managers is is the Organizations UniqueId, which cannot be changed. A user is not a Manager across the app, they are a Manager of specific organization(s).

When a user has for example (“Organizer”, “Colorado”), the system then applies what rights they have on the Colorado state party organization based on their type of Organizer. As an example, as an Organizer they cannot create a child county or campaign organization while an Admin can.

A user can have both SysAdmin and Manager claims.

Attribute file names

For the Certifications, Interests, Skills, & Tags you are asked for the filename for the thumbnail. This filename must be from this library (Icon Experience V5 catalog). You can not upload your own thumbnail.

Soft Delete Users, Organizations, and Tasks

Soft deleting Organizations and Tasks is documented here.

If you have Admin rights (which gives you delete rights in your CRUD+A claims), you can soft delete a user, organization or task.

Soft delete means the record remains in the database but it is marked as deleted and will not be displayed. These records are retained as an audit trail of what was created.

Soft Deleting a User

• All present & future signups for the user will be deleted. No notification is sent.
• The user will be removed as a host for all present & future events they are hosting.
• The user will be replaced as the owner of any present or future tasks they are the owner of. You will be prompted for the replacement owner.
• All claims for the user will be hard deleted.
• The user will be removed as the Organization From user where set. That organization will be set to the replacement user.

Note: As the user still exists in the database, no new user may use their email address.

• You can edit a deleted user’s email to avoid this issue. The recomendation is prepend a @ to it, changing support@tradewindsstudios.us to @support@tradewindsstudios.us as that is an invalid email address and therefore cannot conflict with a future registration.

Hard Delete Users, Organizations, and Tasks

Only do this if required for legal reasons as this removes a record of what has been done in the system.

• You can only hard delete a record that has already been soft deleted.
• Unlike a soft delete, a hard delete also deletes tasks in the past.
• A hard delete of a user will also delete all records of reports about them and reports they submitted.