toolbox org settings
module_toolbox_org_settings
This module can be activated by applying the tag module_toolbox_org_settings to a published basic subpage.
This is to only be used on the Members Toolbox custom subpage_layout landing page.
This tag will render an "Organisation Settings" module for each organisation that the user has a corresponding role tag for.
You can find the current buttons set up in the control panel here:
#Data mappings
For each nested basic page - we create a button with the following:
- Button Text = basic page headline
- Button URL = basic page content
Button Links
The toolbox buttons link to pages relevent to organisations, such as creating organisation events or renewing organisation memberships.
The page content contains the slug or URL, for example to link a button to the Wildlife Camera Orders page just add the slug: /wildlife-camera-orders
Organsation ID Parameter in Links
NOTE: If a button is using one of these it is best to not modify without assistance from For Purpose.
Organisations are seperate profiles from the user, and users can be an admin to multiple organisations. Therefore the organisation id is often passed in the link to let the page know which organisation is being referred to.
A link containing an organisation ID will look something like: /create_event?org_id=12345 where 12345 is the selected organisation id.
In the button URL text, the keyword token {{org_id}} is replaced with the correct organisation ID before it is shown as a button.
There are two main types of link that use the organisation id:
- Passing the organisation id to a standard page, such as creating an event for an organisation:
Example: /create-event?org_id={{org_id}}
- /create-event - the URL for the create event form
- ?org_id= - the querystring parameter - as this form has been built to use passed-in org id values
- {{org_id}} - the token which will be automatically replaced with the given organisation profile ID
Additional example standard links:
/{{org_id}}- links to the profile page for that organisation/submit-a-project?org_id={{org_id}}- submit a project for the organisation/share-post?org_id={{org_id}}- create a post for this organisation/request-event-flyer?org_id={{org_id}}- request an event flyer for this organisation
- Opening a 123 Form on the organisation profile:
The link text /{{org_id}} opens that organisation profile. If the org id was 12345 the link would be https://www.landcaretas.org.au/12345 which is the profile page for that organisation.
This site uses 123 Forms for collecting organisation information, such as membership renewals. To allow pre-filling these forms, the forms are embedded in the organisation profile page (where the information is available).
The particular 123 Form to show is activated with a parameter, such as ?admin=renew-membership.
Example: /{{org_id}}?admin=renew-membership
- /{{org_id}} - this will send the user to the given organisation profile - as profiles use the profile ID as URL
- ?admin=renew-membership - the querystring parameter - this parameter activates the membership renewal form for the given organisation profile. Note the page will automatically show the correct form for the organisation type.
Additional example profile links activating 123 Forms:
/{{org_id}}?admin=new-membership- opens the new membership 123 Form for that organistion/{{org_id}}?admin=renew-membership- opens the renew membership 123 Form for that organistion/{{org_id}}?admin=edit-org-profile- opens the edit profile 123 Form for that organistion/{{org_id}}?admin=edit-org-account- opens the edit account 123 Form for that organistion/{{org_id}}?update-org-photo- this opens an uploader (not a 123 Form) for the organisation to change their profile image
Please see the Forms for Organisations section in the 123 Form Builder Guide for more information on how the 123 Forms are related to these links.
Visibility Restriction by role
By default - all individuals will be able to see all buttons here. However you can apply one of the following tags to restrict visibility.
role:admin- button will only be visible if user has atleast oneadmintag.role:editor- button will only be visible if user has atleast oneeditortag.role:connected- button will only be visible if user has atleast oneconnectedtag.
If a subpage has two tags - for example role:admin and role:editor - the user will only need to have one of these tags to see the button.
Visibility Restriction by membership type
By default - all individuals will be able to see all buttons here. However you can apply one of the following tags to restrict visibility.
org_member:associate- button will only be visible if organisation is an associate member.org_member:associate_school- button will only be visible if organisation is an associate school member.org_member:group- button will only be visible if organisation is an associate member.
If a subpage has two tags - for example org_member:associate_school and org_member:group - the button will be visible for both membership types.