There is a set of standard project roles that can be granted to users of your Mediaflux project. Here we will help you understand which role to grant to each user depending on their use case.
If you have a user that you would like to give read-only access to the content of your Mediaflux project.
participant-a: allow a user to read data. This will allow them to access and download data using all current access methods like the Mediaflux Unimelb Command-Line Clients, SFTP, and SMB.
Depending on the access method the user is going to use, you might grant them either participant-acm or participant-acmd-n.
participant-acm: allow a user to read, upload and modify data. They can create files and directories but cannot delete them. This could make sense for automated or command-line uploads with Mediaflux Unimelb Command-Line Clients or SFTP.
participant-acmd-n: allow a user full read-write access. They can create files and directories and delete them. This makes sense for any interactive access where a user wants to be able to create and modify files, for example Mediaflux Explorer or SMB.
Where your Mediaflux project requires that users have different access levels to different directories, we can offer our Standard ACL Structure .
participant-a: We use the read-only role as the basis for the user’s access. The user is then granted additional access to certain subdirectories or additional restrictions are added to remove their access.
The administrator role grants full read-write access (equivalent to participant-acmd-n), as well as the ability to manage project metadata and queries, grant project roles to other users (though this is typically done by the Mediaflux support team by raising a ticket).
a Mediaflux namespace can be thought of as a folder or directory
a Mediaflux asset is a file and its associated metadata. When you upload a file, Mediaflux makes an asset, puts the file content into the asset, and creates a default set of metadata about the asset including a checksum of the contents of the file. Assets are versioned, so if you modify the file, both versions will be retained in Mediaflux.
The full list of the standard roles per project:
participant-a
access project child namespaces
access project assets
participant-acm
access, create, and modify project child namespaces
access, create, and modify project assets
participant-acmd
access, create and modify (but not destroy) project namespaces
access, create, modify and destroy project assets
participant-acmd-n
access, create, modify and destroy project child namespaces
access, create, modify and destroy project assets
administrator
access, create, modify, and destroy project child namespaces
access, create, modify, and destroy project assets
manage specialised project metadata definitions and queries
grant project access to other users (however, this is best done by the Mediaflux support team by raising a ticket).
Note: modify access is required to move assets or namespaces
If you wanted to give somebody read-only access to your project, then they would be granted the role participant-a
Give a user the role participant-acm if you want them to be able to upload, modify and access files and directories, but not delete them
Give a user the role participant-acmd-n if you want them to have full read-write access files and directories, but not allow them the ability to manage metadata definitions or to grant others access to the project