%TOC% %STARTINCLUDE%

## <a name="TWiki_Access_Control"> TWiki Access Control </a>

%WIKITOOLNAME% allows you to define restrictions of who is allowed to view a %WIKITOOLNAME% web, make changes to topics or attach files.

**IMPORTANT NOTE:** Think twice before restricting read or write access to a web or a topic, because an open system where everybody can contribute is the essence of the %TWIKIWEB%.WikiCulture. Experience shows that unrestricted write access works very well because:

* There is enough peer pressure to post only conform content.
* Content does not get lost because topics are under revision control.
* A topic revision can be undone by a member of the %MAINWEB%.TWikiAdminGroup in case needed.

### <a name="Users_and_Groups"> Users and Groups </a>

Access control is based on users and groups.

**_Users_** are defined by the user topics in the %MAINWEB% web, i.e. %MAINWEB%.TWikiGuest

* Users can be authenticated using basic authentication or SSL. [Installation Notes](TWikiDocumentation#installation) has more.

**_Groups_** are defined by group topics in the %MAINWEB% web, i.e. %MAINWEB%.TWikiAdminGroup

* A group topic name must end in **...Group**
* The group topic should define these two variables:
  * Set GROUP = &lt; list of users and groups &gt;
  * Set ALLOWTOPICCHANGE = &lt; list of users and groups &gt;
* GROUP defines the members of the group; it is a comma delimited list of users and other groups. Example: <br /><code>    \* Set GROUP = %MAINWEB%.SomeUser, %MAINWEB%.OtherUser, %MAINWEB%.SomeOtherGroup</code>
* ALLOWTOPICCHANGE defines who is allowed to change the group topic; it is a comma delimited list of users and groups. You typically want to restrict that to the members of the group itself, so it should contain the name of the topic, i.e. <br /><code>    \* Set ALLOWTOPICCHANGE = %MAINWEB%.TWikiAdminGroup</code><br /> for the TWikiAdminGroup topic. (This is to prevent users not in the group from editing the topic and gaining unauthorized membership to the group.)

### <a name="Write_Access_Restriction_by_Topi"> Write Access Restriction by Topic </a>

You can define restrictions of who is allowed to make changes to a topic or attach files to it.

Define one or both of these variables in a topic, preferably at the end of the topic:

* Set DENYTOPICCHANGE = &lt; list of users and groups &gt;
* Set ALLOWTOPICCHANGE = &lt; list of users and groups &gt;

DENYTOPICCHANGE defines users or groups that **are not** allowed to make changes to the topic. It is a comma delimited list of users and groups. Example: <br /><code>    \* Set DENYTOPICCHANGE = %MAINWEB%.SomeBadBoy, %MAINWEB%.SomeBadGirl, %MAINWEB%.SomeHackerGroup</code>

ALLOWTOPICCHANGE defines users or groups that **are** allowed to make changes to the topic. It is a comma delimited list of users and groups. Example: <br /><code>    \* Set ALLOWTOPICCHANGE = %MAINWEB%.SomeGoodGuy, %MAINWEB%.SomeGoodGirl, %MAINWEB%.TWikiAdminGroup</code>

DENYTOPICCHANGE is evaluated before ALLOWTOPICCHANGE. Access is denied if the authenticated person is in the DENYTOPICCHANGE list, or not in the ALLOWTOPICCHANGE list. Access is granted in case DENYTOPICCHANGE and ALLOWTOPICCHANGE is not defined.

### <a name="Write_Access_Restriction_by_Web"> Write Access Restriction by Web </a>

You can define restrictions of who is allowed to make changes to a %WIKITOOLNAME% web. This includes creating new topics, changing topics or attaching files.

Define one or both of these variable in the %WEBPREFSTOPIC% topic:

* Set DENYWEBCHANGE = &lt; list of users and groups &gt;
* Set ALLOWWEBCHANGE = &lt; list of users and groups &gt;

The same rules apply like the one for Access Control for Individual Topics; with these additions:

* DENYTOPICCHANGE (in topic) overrides DENYWEBCHANGE (in %WEBPREFSTOPIC%)
* ALLOWTOPICCHANGE (in topic) overrides ALLOWWEBCHANGE (in %WEBPREFSTOPIC%)

### <a name="Rename_Access_Restriction_by_Top"> Rename Access Restriction by Topic </a>

You can define restrictions of who is allowed to rename a topic. Note that users need this permission in addition to the CHANGE permission in order to rename a topic. They also need CHANGE access to change references in referring topics.

Define one or both of these variables in a topic, preferably at the end of the topic:

* Set DENYTOPICRENAME = &lt; list of users and groups &gt;
* Set ALLOWTOPICRENAME = &lt; list of users and groups &gt;

DENYTOPICCRENAME defines users or groups that **are not** allowed to rename the topic. It is a comma delimited list of users and groups. Example: <br /><code>    \* Set DENYTOPICRENAME = %MAINWEB%.SomeBadBoy, %MAINWEB%.SomeBadGirl, %MAINWEB%.SomeHackerGroup</code>

ALLOWTOPICRENAME defines users or groups that **are** allowed to rename the topic. It is a comma delimited list of users and groups. Example: <br /><code>    \* Set ALLOWTOPICRENAME = %MAINWEB%.SomeGoodGuy, %MAINWEB%.SomeGoodGirl, %MAINWEB%.TWikiAdminGroup</code>

DENYTOPICRENAME is evaluated before ALLOWTOPICRENAME. Access is denied if the authenticated person is in the DENYTOPICRENAME list, or not in the ALLOWTOPICRENAME list. Access is granted in case DENYTOPICRENAME and ALLOWTOPICRENAME is not defined.

### <a name="Rename_Access_Restriction_by_Web"> Rename Access Restriction by Web </a>

You can define restrictions of who is allowed to do renames for a %WIKITOOLNAME% web.

Define one or both of these variable in the %WEBPREFSTOPIC% topic:

* Set DENYWEBRENAME = &lt; list of users and groups &gt;
* Set ALLOWWEBRENAME = &lt; list of users and groups &gt;

The same rules apply like the one for Access Control for Individual Topics; with these additions:

* DENYTOPICRENAME (in topic) overrides DENYWEBRENAME (in %WEBPREFSTOPIC%)
* ALLOWTOPICRENAME (in topic) overrides ALLOWWEBRENAME (in %WEBPREFSTOPIC%)

### <a name="Read_Access_Restriction_by_Web"> Read Access Restriction by Web </a>

You can define restrictions of who is allowed to view a %WIKITOOLNAME% web.

Define one or both of these variable in the %WEBPREFSTOPIC% topic:

* Set DENYWEBVIEW = &lt; list of users and groups &gt;
* Set ALLOWWEBVIEW = &lt; list of users and groups &gt;

### <a name="Read_Restriction_Known_Issues"> Read Restriction Known Issues </a>

* The view restriction is not suitable for very sensitive content since there is a way to circumvent the read access restriction.
* Read access restriction only works if the view script is authenticated, that means that users need to log on also just to read topics. [TWiki Installation](TWikiDocumentation#installation) has more on basic authentication based on the `.htaccess` file.
* There is a workaround if you prefer to have unrestricted access to view topics located in normal webs, and to authenticate users only for webs where view restriction is enabled:
  * Leave the `view` script non authenticated in the `.htaccess` file.
  * Enable the `$doRememberRemoteUser` flag in `wikicfg.pm` as described in [TWiki Authentication](TWikiDocumentation#authentication). %WIKITOOLNAME% will now remember the IP address of an authenticated user.
  * Copy the `view` script to `viewauth` (or better, create a symbolic link)
  * Add `viewauth` to the list of authenticated scripts in the .htaccess file.
  * When a user accesses a web where you enabled view restriction, %WIKITOOLNAME% will redirect from the `view` script to the `viewauth` script once (this happens only if the user has never edited a topic). Doing so will ask for authentication. The `viewauth` script shows the requested topic if the user could log on and if the user is authorized to see that web.
* If you enable view restriction for a web, it is recommended to restrict search "all webs" from searching this web. Enable this restriction with the `NOSEARCHALL` variable in its [[WebPreferences]], like:
  * Set NOSEARCHALL = on
* It is not recommended to restrict view access to individual topics since all content is searchable **_within_** a web.

### <a name="The_SuperAdminGroup"> The SuperAdminGroup </a>

The above schema can lock completely a topic in case of a typing error of the ALLOWTOPICCHANGE setting (see [UnchangeableTopicBug](http://www.twiki.org/cgi-bin/view/Codev/UnchangeableTopicBug)). To avoid this:

* set the `$superAdminGroup` variable in `TWiki.cfg` to the name of a group of users that are always allowed to edit/view topics. E.g.:

    $superAdminGroup = "TWikiAdminGroup";

* the default setting is not to have superusers

-- [[PeterThoeny]] - 16 Mar 2001 <br /> -- [[AndreaSterbini]] - 11 Apr 2001 <br /> %STOPINCLUDE% **_Related topics:_** %WIKIPREFSTOPIC%, %WEBPREFSTOPIC% (in every web), %MAINWEB%.TWikiAdminGroup, %MAINWEB%.TWikiGroups