Jazz CMS Wiki

• Home Page
• All Pages
• Categories
  

About Us

• WiebeWorks
  

CMS CMS Administration GUI Jazz Jazz Administration Jazz Web Parts Library misc Roles Solutions Training Web Parts Web Service Website Design Website Procedures Wiki conventions WordML Workflow Administration

Quick Search
»
Advanced Search »

Registration Solution: Roles and Workspaces

Table of Contents [Hide/Show]    Registration Solution: Roles and Workspaces        Securing Workflows          Why use the same name for the Club, Workspace and Role?          How does this secure the data?          Some Properties are Read-Only for the Club Administrator. How does that work?

Registration Solution: Roles and Workspaces¶

Roles and Workspaces are used to secure data for the Registration Solution.

Data isolation is provided by using Workspaces and Roles.

• The Workspace for "Club A" is assigned a Club Role to the ACL (Access Control List).
• The Workspace for "Club A" is also assigned the Registrar Role to the ACL.
• Each Club Administrator for "Club A" is assigned the same Club Role that matches the Workspace Role.
• The Registrar can access the data in "Club A".
  

Securing Workflows¶

Let's walk through an example of how Workflows are secured. The example secures data for the XYZ Club.

Club Name: 'XYZ'

To secure the club data, follow these steps:

1. Create a unique Workspace for every Club. The Workspace name is 'XYZ'.
2. Create a unique Role. The Role name is 'XYZ'.
3. Add the 'XYZ' Role to the 'XYZ' Workspace.
4. Create a User, who will be the Club Administrator. e.g. this may be 'Sally' or 'Sally@XYZ.com'.
5. Add the 'XYZ' Role to the new User.
6. The new User logs in.
7. Add Club data.
8. Add Members to the Club.
9. Add Profiles to each Member.
   

Why use the same name for the Club, Workspace and Role?¶

The same name is used to define the club, workspace and Role. This can be confusing if you need to talk about Club, Workspace and Role separately. e.g. "I use the 'XYZ' Role to secure the data for the 'XYZ' Club in the 'XYZ' Workspace." Only a Jetfire Administrator needs to think about the Club, Workspace and Role as separate entities.

In general, the Club Adminstrator (a Jetfire User) for the 'XYZ' Club says "I manage the data for the 'XYZ' Club." The Club, Workspace and Role are blurred into a single entity - the Club.

When asked about Club 'XYZ', both the Jetfire Administrator and the Club Administrator understand the relationship to the data.

How does this secure the data?¶

Jetfire Data Security is performed when the User logs in. This is what happens:

1. The Jetfire User logs in.
2. Roles for the Jetfire User are compared to Roles in the Workspace ACL (Access Control List).
   1. If the Roles match, then the workspace and its data is retrieved for the user.
   2. If the Roles do not match, then the workspace and its data is not visible to the user.
      

Some Properties are Read-Only for the Club Administrator. How does that work?¶

When the data is retrieved, the Roles for the logged-in user are compared to the Roles in the Property ACL. Properties that do not allow the Club Administrator to write to the property are identified at this time, thus making the property read-only.

For more information, read about dynamic access modifiers.