ownloads Documentation Centre!Limited Access Example - A Members Organisation
Introduction
In a membership organisation or similar each member may require to keep details of some Downloads confidential. That is in some situations it required to limit access of some Downloads as private to individual members. Also there may be a requirement where a 'supervisor' needs to also add some downloads for a group of members.
This achievable with a combination of Permissions and View Access Levels.
In this example we have used 3 members called MemberA, MemberB and MemberC with a 'supervisor' called MonitorABC. That is A, B and C denote which member.
Once the basic structures are set up then it is straightforward to add additional members.
This achievable with a combination of Permissions and View Access Levels.
In this example we have used 3 members called MemberA, MemberB and MemberC with a 'supervisor' called MonitorABC. That is A, B and C denote which member.
Once the basic structures are set up then it is straightforward to add additional members.
See also Controlled Access to Categories and Downloads (opens in a new tab) for other examples.
Basic Setup
There are five parts which need to be setup:
1. User Groups
2. View Access Levels
3. Users
4. Categories
5. Menu Items
1. User Groups
2. View Access Levels
3. Users
4. Categories
5. Menu Items
User Groups
The first step is to create a User Group for each member, even if we have not yet added the member as a user.
Personally I find it helpfull to add the trailing '-ug' to each User Group.
In this example they are called memberA-ug, memberB-ug and memberC-ug.
Also create a User Group for the Supervisor which is called here as monitorABC-ug.
In all cases the parent User Group is Registered
Personally I find it helpfull to add the trailing '-ug' to each User Group.
In this example they are called memberA-ug, memberB-ug and memberC-ug.
Also create a User Group for the Supervisor which is called here as monitorABC-ug.
In all cases the parent User Group is Registered
Note you will also need to set the jDownloads UG's to have the appropriate settings - do not forget to set the ranking level to say 131, 132 and so on. See User Groups Overview for more information (opens in a separate tab).
View Access Levels
Create the access levels,which are called here memberAview, memberBview and memberCview. And assign the appropriate User Groups.
Also create a view for the Monitor, which is called monitorView in this example.
Also create a view for the Monitor, which is called monitorView in this example.
The Access levels each have their 'member UG' and also monitorABC as illustrated above.
Users
Having setup the User Groups and the Access Levels, it is convenient to now create the users.
It is simpler to do this at this juncture as we have already created the user group to which the user will be assigned and so avoids having to go back to the User Management.
The final setup for the Users is shown opposite.
It is simpler to do this at this juncture as we have already created the user group to which the user will be assigned and so avoids having to go back to the User Management.
The final setup for the Users is shown opposite.
Categories
Each Member is given a top level Category, called in this example as 'memberAcat' and so on.
As noted later it is these top level categories where we will setup the permissions.
Then create appropriate subcategories, which includes the members name or similar 'ID' for various 'topics' and 'reports'.
Note the setting of the view Access Levels.
As noted later it is these top level categories where we will setup the permissions.
Then create appropriate subcategories, which includes the members name or similar 'ID' for various 'topics' and 'reports'.
Note the setting of the view Access Levels.
Permissions
At this stage we need to decide which permission to give each member and those for the 'monitor' user Group.
We only need to set the permission in the Top level Categories as they will cascade down to the the sub categoies and then to the Downloads.
Note that when jDownloads is installed the first time it will create Download Permission in the so called Component Permissions.
So we could leave Download permission as Inherited.
We only need to set the permission in the Top level Categories as they will cascade down to the the sub categoies and then to the Downloads.
Note that when jDownloads is installed the first time it will create Download Permission in the so called Component Permissions.
So we could leave Download permission as Inherited.
We also need to set the Permisions for the 'monitor' in each top level category.
Menu Items
Each member should have a Single Category menu item that will list their top level category.
They must be set set with the relevant view access level.
Also there could be a List My Downloads menu item that has a Registered view access level.
For this menu item to work then every Download needs to have the 'creator' set as noted below.
They must be set set with the relevant view access level.
Also there could be a List My Downloads menu item that has a Registered view access level.
For this menu item to work then every Download needs to have the 'creator' set as noted below.
It is useful if the 'monitor' has a list All Categories type menu item.
Download creator
When the 'monitor' is creating a Download for a member ensure that in the option Publishing tab that the 'Created by' pulldown is used to select the member as the creator.
If it is the relevant member who is creating the Download then jDownloads automatically sets this option appropriately.
Examples
The List My Downloads view shown is dependant on who is logged in.
View shown opposite is when MemberA is logged in.
This is the view when using the menu item 'memberAcategory' is used.
The pulldown list only shows the relevant items.
Similarly the Overview and All Downloads will only show the appropriate items relating to whom is logged in.
ColinM April 2022
Tags: index