Space Hierarchy Licence Agreement
TechTime Initiative Group Limited Software License Agreement
No more mess. Create self-managed spaces and place pages into clean hierarchies automatically.
An add-on that allows you to save newly created pages into a specific place in the space hierarchy structure automatically.
There are times when the content within a space is to retain a specific hierarchical page structure, and all newly created pages must integrate seamlessly with the existing hierarchy.
Ensuring that a newly created page is created correctly within the page hierarchy is often not an issue for experienced users of Confluence, however for the novice user, the availability of the "Create" button from all pages can lead to confusion as to where their new page is going to integrate into the existing space hierarchy. This confusion often leads to disorder and disorganisation within the space resulting in "pile" of content with no clear structure
With Space Hierarchy, regardless of the level of the page the user is viewing, when they select the 'create' button the newly created page will automatically be saved to the correct hierarchical level within the space.
Space Hierarchy can be utilised on pages created using the default blank page template, or from pages created using the Blueprint Wizard tool to impose selection by the user of pre-determined categories or geographical regions which then become the associated labels. Upon saving the newly created page, the Space Hierarchy will automatically determine where in the existing page hierarchy the new page should be shown.
Space Hierarchy will reduce the amount of time space administrators have to spend reordering the hierarchy to ensure all content is viewable to the right audience. Space Hierarchy will also reduce the disorder and user confusion that can result when pages are not viewable or not in the order expected.
When users inadvertently select the "Create" button while viewing a child page their newly created page becomes a "grandchild" page. In many cases, a flat, single-level hierarchy may be preferred instead.
Content within the space may be organised by specific categories or geographic regions which have been determined from labels. This allows you to create a self-maintaining space hierarchy by the pre-defined labels that are contained within the Blueprint Wizard tool that is evoked when a page within the space is created.
The selection of a category automatically assigns the associative labels to the newly created page. This new page is then automatically moved into the hierarchical structure associated with the labels, ensuring a structural order of the space is maintained.
There may be some content that has restricted access within the user group of the space. This may be because the content of these pages is confidential, or the page may no longer be relevant to the current discussion i.e. archived. The selection of the specific label to a page, either manually or automatically with the Blueprint Wizard, ensures that the page with these specific labels is placed in the correct hierarchy and then inherits the associated page access restrictions e.g. the label of 'archived' restricts viewing of the page to space moderators or administrators, or the label 'confidential' on a new or existing page restricts viewing to a specific managerial group.
Once installed, the "Space Hierarchy" tab is available to space administrators.
In the default "Global Look & Feel" theme - it will be under Space Tools/Integration
In the Documentation theme - it will be under Space Admin/Add-Ons in the left panel.
There, Space Hierarchy can be enabled per space, and the supported hierarchy mode, chosen.
Once enabled the hierarchy will be enforced:
To use the Label to Page hierarchy you will need to configure which labels match to which parent pages.
For example, if you have a page called "Vegetables" and you want any page with the label "carrot" or "broccoli" to automatically become a child of the "Vegetables" page then you would configure like so:
You can set Restrictions by using the following commands:
(where it states 'User', use the person's username for Confluence)
|"unlockViewAll"||enables everyone with Confluence access to view the created page|
|"unlockEditAll"||enables everyone to edit|
|"unlockViewGroup" e.g. lockViewUser:confluence-users||enables a certain group to view the page|
|"unlockEditGroup"||enables a certain group to edit the page|
|"lockViewGroup"||lock the viewing of the page to a certain group|
|"lockEditGroup"||lock the editing of the page to a certain group|
|"lockViewUser" e.g. lockViewUser:johnSmith||lock the viewing of the page to the specified user|
|"lockEditUser"||lock the editing of the page to the specified user|
|"unlockViewUser"||enable viewing for the specified user|
|"unlockEditUser"||enable editing for the specified user|
|"lockCreator"||lock viewing and editing the page to the creator|
|"unlockCreator"||unlock viewing and editing to the page to the creator|
The commands can be chained together to make complex rules. For Example,