<?xml version="1.0" encoding="utf-8"?>
<s1 title="HelpOnAutoAdmin"><p></p>
<s2 id="Auto Admin" title="Auto Admin">
<p><p>Contents</p>
<ol><li>
<link anchor="A">Auto Admin</link><ol><li>
<link anchor="A-1">AutoAdmin usage</link><ol><li>
<link anchor="F">For a personal homepage</link></li>
<li>
<link anchor="F-1">For a project page</link></li>
</ol>
</li>
<li>
<link anchor="A-2">AutoAdmin configuration and administration</link><ol><li>
<link anchor="C">Configuration</link></li>
<li>
<link anchor="A-3">Administration</link><ol><li>
<link anchor="E">Enabling a home page for AutoAdmin</link></li>
<li>
<link anchor="E-1">Enabling another (project) page for AutoAdmin</link></li>
</ol>
</li>
</ol>
</li>
</ol>
</li>
</ol>
<p> The security policy <code>autoadmin</code> included in <jump href="/wiki/MoinMoin">MoinMoin</jump> distribution (but NOT activated by default, see below) is useful when you want to automatically and implicitly give some users or user groups <code>admin</code> rights on some pages. </p>
<p>Having <code>admin</code> rights means being able to create or change ACLs, see <jump href="/wiki/HelpOnAccessControlLists">HelpOnAccessControlLists</jump>. </p>
<p></p>
<s3 id="AutoAdmin usage" title="AutoAdmin usage">
<p></p>
<s4 id="For a personal homepage" title="For a personal homepage">
<p>Check if there is a <jump href="/wiki/HomepageTemplate">HomepageTemplate</jump> with prepared ACL lines or some other already-configured configuration settings. </p>
<p>It is important to ensure your homepage is easily readable and writeable so it can be used as an open form of communication by everyone.  </p>
<p>The easiest way to create personal (or private) subpages for your homepage is to use the MyPages action.  </p>
<p>Alternatively you can also do it manually, using the <jump href="/wiki/HomepageReadWritePageTemplate" class="nonexistent">HomepageReadWritePageTemplate</jump>, <jump href="/wiki/HomepageReadPageTemplate" class="nonexistent">HomepageReadPageTemplate</jump> or <jump href="/wiki/HomepagePrivatePageTemplate" class="nonexistent">HomepagePrivatePageTemplate</jump>. They usually have some prepared ACL line on them, e.g.: </p>
<source><![CDATA[#acl @ME@/ReadWriteGroup:read,write @ME@/ReadGroup:read]]></source><p>That @<code></code>ME@ in the template will be expanded to your name when saving, so those 2 subpages (<code>YourName/ReadWriteGroup</code> and <code>YourName/ReadGroup</code>) of your homepage will be used for allowing read/write or read-only access. </p>
<p>Now you only have to maintain those two subpages (based on <jump href="/wiki/HomepageGroupsTemplate" class="nonexistent">HomepageGroupsTemplate</jump>) of your homepage (maybe they even have been auto-created for you) and put the people on them for allowing them access. </p>
<p></p>
</s4>
<s4 id="For a project page" title="For a project page">
<p>See if there is some <code>&lt;ProjectName&gt;Template</code> with a prepared ACL line for your project pages and use it for creating new subpages. </p>
<p>Use <code>&lt;ProjectName&gt;/ReadWriteGroup</code> and <code>&lt;ProjectName&gt;/ReadGroup</code> etc. as you would do for a homepage (see above). </p>
<p></p>
</s4>
</s3>
<s3 id="AutoAdmin configuration and administration" title="AutoAdmin configuration and administration">
<p></p>
<s4 id="Configuration" title="Configuration">
<p>Add this to your wiki&apos;s configuration file: </p>
<p></p>
<source><![CDATA[    # indent the line below like your other settings:
    from MoinMoin.security.autoadmin import SecurityPolicy]]></source><p>Create an <jump href="/wiki/AutoAdminGroup" class="nonexistent">AutoAdminGroup</jump> page. It is usually a good idea to create an empty page for this. </p>
<p>That page (and also other group pages used with autoadmin, see below) should be ACL protected with write access limited to allowed people. They are used as source for some ACL information and thus should be treated like the ACLs they get fed into. </p>
<p></p>
</s4>
<s4 id="Administration" title="Administration">
<p></p>
<s5 id="Enabling a home page for AutoAdmin" title="Enabling a home page for AutoAdmin">
<p>Just add the user name (same as home page name) to the <code>AutoAdminGroup</code> page. Alternatively, if you want to enable this feature for all users of some specific group, add the group page name to <code>AutoAdminGroup</code>. </p>
<p>All users directly or indirectly on <code>AutoAdminGroup</code> will get <code>admin</code> rights on their own homepage or subpages of it. </p>
<p>This is needed for the MyPages action, but can also get used for manual ACL changes. </p>
<p>You also can define some page templates with pre-made ACLs for them to use for new homepages or subpages of it. </p>
<p></p>
</s5>
<s5 id="Enabling another (project) page for AutoAdmin" title="Enabling another (project) page for AutoAdmin">
<ol><li><p>Add <code>&lt;PageName&gt;/AdminGroup</code> to <code>AutoAdminGroup</code>. </p>
</li>
<li><p>Also create that <code>&lt;PageName&gt;/AdminGroup</code> group definition page and add at least one user or one group to that page, giving them <code>admin</code> rights on <code>&lt;PageName&gt;</code> or subpages of it. </p>
</li>
</ol>
</s5></s4></s3></s2></s1>