Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The superuser admin can add new superusers to the special d (default tenant). New Users added to the default tenat automatically become new superusers. This allows you to name additional superusers and then if you want you can disable the built-in superuser named "admin". To disable the build-it superuser named "admin" click the button above the alpabet list. This brings you directly to the build-in superuser admin's edit page, or you can click the  icon to the right of the admin name in the user list. Set the Enabled dropdown to false. This will prevent further logins by the built-in superuser named "admin". Note you cannot delete the built-in superuser named "admin". You can however delete any additional admin user you have created.

Edit Users

Click the Image Added button next to any user in the users list to edit that user. You can perform functions such as adding/removing roles, resetting paswords, etc...

Edit Admin Users 

There is also a short-cut to edit the initial tenant admin – click the Image Addedbutton above the alphabet list to go directly to the initial tenant admin's edit page. You can also distinguish the initial tenant admin from non-admins because the initial tenant admin cannot be deleted so it does not have the Image Added button. If you added additional tenant admins, the user list does not make it readily apparent that a user has that special admin access permission. Currently the way to distinguish an admin is click on each user's Image Added button and see if the user has the Manage Tenant functions. 

 

Disable Users

The superuser or tenant admin can disable a user. Disabling a user prevents that user from logging into the form server. If the user was had the role frevvo.designer (aka. was a designer user) the users' forms will become inaccessible to other users. Even if the forms were public users will get the error "This resource belongs to a disabled user". To disable a designer user but keep the form accessible, change the user's role from frevvo.designer to frevvo.readonly and set the Enabled dropdown back to true. In this case when the user tries to login they will get the error "Login is currently disabled".

...