Geeklog Permissions - Revision history

Dirk: quick introduction into read/write access

2009-05-27T13:32:42Z

quick introduction into read/write access

Dirk: Link to FAQ

2009-05-27T13:25:24Z

Link to FAQ

Dirk: added a note about changing the default permissions

2009-05-15T12:54:03Z

added a note about changing the default permissions

Vinny: =Interactions of Article and Topic Permissions=

2004-07-19T01:56:09Z

=Interactions of Article and Topic Permissions=

Vinny at 01:54, 19 July 2004

2004-07-19T01:54:37Z

New page

The best way to learn about Geeklog permissions is to try things out and
see what happens.

== Interactions of Article and Topic Permissions ==

If you want a user to be able to edit an article that they are the owner
of they need both READ and EDIT permissions for both the article and the
topic to which that article belongs.

The thinking behind this is that you should not be able to edit an
article (even if you originally wrote it and/or are the current owner)
unless you have edit permissions for the topic as well. This allows a
site Admin to restrict certain types of access to a given topic.
Granted, this is not the simplest thing to understand and it perhaps
should be rethought. However, since its been this way for several
major releases now it is unlikely it will be changed unless there is an
over riding reason to do so.

This is not a security hole because you need read/edit for *both* the
article you want to edit and the topic that it is in. Again, it just
allows the Geeklog admin a much finer level of control.

← Older revision		Revision as of 13:25, 27 May 2009
Line 22:		Line 22:

	'''Note:''' The default permissions can be changed in the Configuration admin control panel: Configuration > Geeklog > Miscellaneous. Scroll down to "Story Default Permission" and "Topic Default Permission".		'''Note:''' The default permissions can be changed in the Configuration admin control panel: Configuration > Geeklog > Miscellaneous. Scroll down to "Story Default Permission" and "Topic Default Permission".
		+
		+	Also see the Geeklog FAQ: [http://www.geeklog.net/faqman/index.php?op=view&t=23 Setting up a Story Admin]

@@ Line 1: / Line 1: @@
-The best way to learn about Geeklog permissions is to try things out and
+The Geeklog permissions are (loosely) based on the concept borrowed from UNIX file systems: Geeklog objects (e.g. stories) have "read" and "write" access permissions. Those can further be restricted by groups and their owner.
 see what happens.
 == Interactions of Article and Topic Permissions ==

@@ Line 6: / Line 6: @@
 If you want a user to be able to edit an article that they are the owner
 of they need both READ and EDIT permissions for both the article and the
-topic to which that article belongs.
+[[Topics|topic]] to which that article belongs.
 The thinking behind this is that you should not be able to edit an
@@ Line 20: / Line 20: @@
 article you want to edit and the topic that it is in.  Again, it just
 allows the Geeklog admin a much finer level of control.

@@ Line 17: / Line 17: @@
 over riding reason to do so.
-This is not a security hole because you need read/edit for *both* the
+This is not a security hole because you need read/edit for ''both'' the
 article you want to edit and the topic that it is in.  Again, it just
 allows the Geeklog admin a much finer level of control.