r26 - 2013-08-28 - 11:43:06 - StevenBeardYou are here: TWiki >  Deployment Web > DeploymentAccessControl

Access control for the Deployment wiki

Authors: StevenBeard
Build basis: None

This topic outlines the different levels of access control to the wiki, with supporting guidance on when and how to change the levels for specific topic pages.

Levels of access control to the Deployment wiki

Read access to the Deployment wiki is unrestricted. You do not even need to log in with your Jazz.net user ID for full read access, which facilitates external search engine indexing and search, such as Google.

Three groups are used to control write access to all topic pages:

  • Jazz.net users: All Jazz.net users have write access to open community topic pages by using their Jazz.net user ID and password. This group is enabled by the Jazz.net users LDAP group.

By default, write access to all wiki pages is restricted to the TWikiDeploymentAuthorsGroup. Subsequently the community or section technical leaders and senior editors can open a page for wider write access to the Deployment practitioners (TWikiAuthorsGroup and TWikiExternalAuthorsGroup) or Jazz.net users (Jazz.net LDAP group). The granting of wider write access must occur on a page-by-page basis.

Many topic pages will be created by the technical leaders and senior editors, and then opened for wider write access to the Deployment practitioners or Jazz.net users. However, some core pages that contain fundamental or critical guidance and best practices will be editable only by the technical leaders and senior editors. It is important to strike the right balance between core pages that are editable only by experts to maintain a high quality versus community pages that allow the full community to contribute. Many of the core pages allow comments and questions to be raised to enable wider community contribution.

Changing the level of write access control for a topic page

The color of the title box at the top of each page denotes the level of write access. This will give a clear visual cue as to who can edit a page, and the provenance and quality of the guidance on that page. Below are illustrations of the three title box colors and the verbatim Twiki mark-up, with access control required for each:

Technical leaders and senior editors

Authors: StevenBeard
Build basis: None

 
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! Technical leaders and senior editors
%DKGRAY% Authors: Main.StevenBeard <br>
Build basis: None
%ENDCOLOR%</div></sticky>

Deployment practitioners

Authors: StevenBeard
Build basis: None

 
<!--
   * Set ALLOWTOPICCHANGE = Main.TWikiDeploymentAuthorsGroup, Main.TWikiAuthorsGroup, Main.TWikiExternalAuthorsGroup
-->
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#A8CEE4; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/DP.jpg); background-size: cover; font-size:120%">
---+!! Deployment practitioners
%DKGRAY% Authors: Main.StevenBeard <br>
Build basis: None
%ENDCOLOR%</div></sticky>

Jazz.net users

Authors: StevenBeard
Build basis: None

 
<!--
   * Set ALLOWTOPICCHANGE = 
-->
<sticky><div id="container" >
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#A8CEE4; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/DP.jpg); background-size: cover; font-size:120%">
---+!! Deployment practitioners
%DKGRAY% Authors: Main.StevenBeard <br>
Build basis: None
%ENDCOLOR%</div></sticky>

Note: Be careful when you set the write access for a topic (ALLOWTOPICCHANGE), because it is very easy to make the wrong selection and remove write access for yourself and others.

Write access groups TWiki/LDAP group Border color Background image
Technical leaders and senior editors TWikiDeploymentAuthorsGroup #FFD28C WebPreferences/TLASE.jpg
Deployment practitioners TWikiAuthorsGroup and TWikiExternalAuthorsGroup #A8CEE4 WebPreferences/DP.jpg
Jazz.net users Jazz.net LDAP group #DFDFDF WebPreferences/Users.jpg

Detailed steps required to gain different levels of write access

Open community topic page write access for Jazz.net users

For this level of write access, no additional steps are required other than to register as a Jazz.net user. This level of write access will be enabled for all existing Jazz.net users and any newly registered Jazz.net users going forward. You must log in with your Jazz.net credentials to edit an open community topic page.

Deployment practitioner topic page write access for IBMers

IBMers only need to follow the steps to Request write access for IBMers. No additional approval steps are required, and write access to deployment practitioner topic pages and membership of the Deployment wiki project on Rational Team Concert should be enabled within a few days.

This user will be added to these groups:

  1. The jazzwriter's LDAP group
  2. The TWikiUsers list
  3. The TWikiAuthorsGroup
  4. The membership of the Deployment wiki project on Rational Team Concert

Deployment practitioner topic page write access for customers and IBM Business Partners

To request this level of write access, all customers and IBM Business Partners must follow the deployment practitioner nomination process. The nomination will then be approved or rejected by a combination of the IBM sponsor for the nomination and one of the community technical leaders and senior editors.

If approved, the user is emailed that the nomination was accepted and that the user is set up for this level of write access.

This user will be added to theses groups:

  1. The jazzwriter's LDAP group
  2. The TWikiUsers list
  3. The TWikiExternalAuthorsGroup
  4. The membership of the Deployment wiki project on Rational Team Concert

Technical leader and senior editor topic page write access for IBMers

Note: To request this level of write access, IBMers must first request Deployment practitioner topic page write access.

Then, IBMers must follow the deployment technical leaders and senior editors nomination process. The nomination will then be approved or rejected by the full community technical leaders and senior editors.

If approved, the user will be added to the TWikiDeploymentAuthorsGroup.

Technical leader and senior editor topic page write access for customers and IBM Business Partners

To request this level of write access, customers and IBM Business Partners must follow the deployment technical leaders and senior editors nomination process. The nomination will then be approved or rejected by a combination of the IBM sponsor for the nomination and the full community technical leaders and senior editors.

If approved, the user will be emailed that the nomination was accepted and that the user is set up for this level of write access.

This user will be added to these groups:

  1. The jazzwriter's LDAP group
  2. The TWikiUsers list
  3. The TWikiExternalAuthorsGroup
  4. The TWikiDeploymentAuthorsGroup
  5. The membership of the Deployment wiki project on Rational Team Concert

Related topics: Deployment Wiki Request Write Access for IBMers, Deployment technical leaders and senior editors nomination process, Deployment practitioners nomination process

External links:
  • None

Additional contributors: None

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r26 < r25 < r24 < r23 < r22 | More topic actions
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Ideas, requests, problems regarding the Deployment wiki? Create a new task in the RTC Deployment wiki project