<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://wiki.freedesk.purplepixie.org/w/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
		<id>http://wiki.freedesk.purplepixie.org/w/index.php?action=history&amp;feed=atom&amp;title=Permissions</id>
		<title>Permissions - Revision history</title>
		<link rel="self" type="application/atom+xml" href="http://wiki.freedesk.purplepixie.org/w/index.php?action=history&amp;feed=atom&amp;title=Permissions"/>
		<link rel="alternate" type="text/html" href="http://wiki.freedesk.purplepixie.org/w/index.php?title=Permissions&amp;action=history"/>
		<updated>2026-05-12T23:05:14Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.19.0</generator>

	<entry>
		<id>http://wiki.freedesk.purplepixie.org/w/index.php?title=Permissions&amp;diff=58&amp;oldid=prev</id>
		<title>Dave: Created page with &quot;Permissions in FreeDESK operate on a granular most-specific model.  Each user can have permissions assigned to it directly or be a member of a permissions group for easy bulk ...&quot;</title>
		<link rel="alternate" type="text/html" href="http://wiki.freedesk.purplepixie.org/w/index.php?title=Permissions&amp;diff=58&amp;oldid=prev"/>
				<updated>2012-08-21T22:37:08Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;Permissions in FreeDESK operate on a granular most-specific model.  Each user can have permissions assigned to it directly or be a member of a permissions group for easy bulk ...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Permissions in FreeDESK operate on a granular most-specific model.&lt;br /&gt;
&lt;br /&gt;
Each user can have permissions assigned to it directly or be a member of a permissions group for easy bulk administration.&lt;br /&gt;
&lt;br /&gt;
A wide variety of operations are assigned a permission (these are either coded within the system or added automatically by plugins once installed). These permissions can be explicitly set (allowed or denied) on a per-user or per-group basis. If a permission is undefined then the next level of specificity is tested (hence the most-specific model).&lt;br /&gt;
&lt;br /&gt;
When a permission is requested it is determined as follows:&lt;br /&gt;
&lt;br /&gt;
* Is the permission set specifically for the user (allowed or denied), in which case this is used.&lt;br /&gt;
* Does the user have a default permission (allowed or denied), in which case this is used.&lt;br /&gt;
If the user is a member of a permission group:&lt;br /&gt;
* Is the permission set specifically for the group (allowed or denied), in which case this is used&lt;br /&gt;
* Does the group have a default permission (allowed or denied), in which case this is used&lt;br /&gt;
If no matching permission is found:&lt;br /&gt;
* Permission Denied&lt;br /&gt;
&lt;br /&gt;
= Examples =&lt;br /&gt;
&lt;br /&gt;
== One ==&lt;br /&gt;
&lt;br /&gt;
The permission &amp;quot;one&amp;quot; is set as denied for the permission group, the user has it and default undefined.&lt;br /&gt;
&lt;br /&gt;
Permission is denied.&lt;br /&gt;
&lt;br /&gt;
== Two ==&lt;br /&gt;
&lt;br /&gt;
The permission &amp;quot;two&amp;quot; is set as denied for the permission group, the user has it undefined but default is allowed.&lt;br /&gt;
&lt;br /&gt;
The permission is allowed.&lt;/div&gt;</summary>
		<author><name>Dave</name></author>	</entry>

	</feed>