Modules:
Manage Page
Webuser Account
Roles Management
Search
MediaPlayer
RSS / XML Feeds
Templates
CMSConfig
DIFF
Placeholders:
Placeholder Intro
Ad Popup
Ad Rotator
Calendar
Comment
dbReport
dbQuery
Forms
Gallery
iFrame
ImageBook
LightBox
MessageBoard
PBReport
PicLens
Query Wrapper
Random Content
Redirect
Security Wrapper
TabStrip
Time Wrapper
Variable Tags
WebPage Rotator
Usage Examples:
Playground
Page Comments
Advanced:
Admin Reports
CMS MEtrics
CMS Setup
Full-text indexing
Configuration
Menus
CSS
xstandard editor
TinyEditor
EditArea Editor
ASPEmail
Debug
Heartbeat
CAPTCHA
Session Variable
Cookies
Tracking
New Module
New Placeholder
New Wrapper
New Form Validation Rule
Roles Management
|
As long as your logged in and have administrator rights over at least ONE role, you can build security strings for ALL ROLES in the system. Search for the webusers you want included. Choose from the Service Roles and System roles. When the Security String is interpreted, the webuser either has to be explicitly name, or a member of the Service Role. To decode an existing security string, Paste the string into the primary text box, and choose [Decode]. To see a list of people and their email addresses for any give security string, choose [Get Email List] /roles?action=builder&decode=mySecurityString decodes a security string as well, where mySecurityString is the string you wish to decode. |
You can paste the email list into outlook for easy emailing, or use Notepad to replace the ; character to , character if you are using another email client. |
All existing services are listed complete with their roles (if they exist). The list includes:
The list or roles and services is reduced to what the person logged in has role management rights for - and they must have role management rights for at least ONE service in order to see the page. Therefore you'll only be able to interact with what you are an role management rights for.
|
The list includes:
A new role for the service can be created, assign a unique name, a description, and then choose if the role is default for new users, subscribable from the profile, and if administrative approval is required for a webuser to be approved for a role. |
BY DEFAULT each new role is bound to the USER role. IF the Role is not bound to at least 1 system role, a web user will not be associated with the role. The properties of the role can be edited, and you can bind and unbind system roles to the role. System roles bound to roles control what ADDITIONAL things can be done by members of the role in the CMS. IF members of the role need to administer over the service, edit webpages, manage security then you should bind the appropriate system: role. All other sys roles are webmaster defined and a global way to track additional information like 'user' - but the CMS does not interact with these additional Sys roles. |
The person must have an account on the system in order to have a role. IF you don't find the person you looking for, have them create an account before you continue. You may add them to more roles, or remove them from an existing role by adding them to the role and choose the status: REMOVE FROM ROLE. Notes are optional. The "User Info x' fields allow you to track your own informatoin and are ignored by the CMS. You can use these fields to tie the CMS into other systems like UCAN. Click the 'edit' link in a users role list to edit their presence in a role up update that roles attributes. |
In the Webuser profile you can choose a role and REMOVE FROM ROLE status to remove a webuser from a role. |
This reports:
|












