Summary

If you are authorised, submit a Service Now ticket!

Adding/Removing People to/from Your Project

Only specific people are allowed to request access for other people to a specific collection (Mediaflux project).  These people are

• The Research Computing Activity Owner. The RCAO is the person with delegation accepting responsibility for the University resources being utilised for this collection (see details here). The RCAO is generally a senior Researcher.
• A Technical Contact (TC) (can be many).

Typically, the person requesting a Mediaflux project to hold the collection is made the 'administrator' of the Mediaflux project.  This person may be the RCAO, but more likely they are a Technical Contact. RCAOs and TCs can find details about the collections they are associated with on the  Storage Dashboard. Note to access the Storage Dashboard you will need to be at the University or connected to the University VPN.

If the person that is to be added to the Mediaflux project is external to the University,  then

• this request can only be made by the RCAO (or someone this responsibility has been delegated to, such as one of the Technical Contacts)
• there is some additional process to be undertaken that is described here

If you are authorised to request the person be added/removed to/from the project, then you can submit a Service Now request for this using one of the  links on this page. In your ticket, specify

• The name of your Mediaflux project
• The name and email address of the person you wish added/removed
• If the person being added is external, include the statement (or email paste) that they have accepted our T&Cs (see above)
• What role you would like them to have in your project. The possible roles are described here.
  • The permissions associated with this role apply everywhere in the project, unless permissions are modified by an ACL (see section below).

Modifying Permissions Of Project Folders

It is common to want to modify the permissions of a folder in your project.  You might want to

• Restrict the folder so that only specific users or roles can access it
• Increase the permissions of a user
  • For example, a user who holds the participant-a (read-only) project role, may need to have their permissions increased to allow them to create data in a specific folder and children folders.
• Decrease the permissions of a user
  • For example, a user how whole the 'participant-acmd' (read/write/destroy) project role, may need to have their permissions decreased to allow them to read-only in a specific folder and children folders.

For any of these (or possibly other!) use cases, if you are the RCAO or Technical Contact for the project, please submit a Service Now request  using one of the  links on this page. In your ticket, specify

• The name of your Mediaflux project
• The user(s) of interest
• How you want to modify their permissions (see also the list of possible roles)

Finally, if you are finding that your ACLs are getting too complex, you might like to consider re-factoring the structure into multiple projects (each with their own list of users and roles).