Principal Investigators (PIs) and researchers from any division are invited to request storage.
There are two service requests for RFS. The first stage is to request RFS storage:
Please ensure you discuss your research storage requirements with your local IT Support team before requesting RFS storage, to ensure RFS is the most appropriate place for your research data. A decision tree has been created to help with this.
Owners will receive a confirmation email that your RFS storage has been set up. Once you map your drive to \\connect.ox.ac.uk\RFS (instructions are in the RFS users' guide) you will see any projects you’ve been given access to.
With this service request, you can also:
-
Request for a project to leave RFS storage
-
Change the amount of RFS storage
-
Change the end date or when RFS storage is required until
-
Change RFS owners
The second stage is to request access for users:
-
All RFS users need a CONNECT AD account. Users or project owners can request these through the RFS User Access service request. You need to do this only once for each user. If a user already has a CONNECT AD account, you can skip this step.
-
If you are one of the named project owners and you do not already have a CONNECT AD account, a CONNECT AD account will be set up for you by default when you first request storage. There is no need to raise a separate RFS User Access service request. We do ask that you name two owners, in case one leaves or is absent.
Once a new User Access request has been actioned, the owners of the storage will be able to manage RFS read-only or read/write access to their project data for this user. Details of how to do this and how to review the amount of storage available using Active Roles Server are provided in the RFS owners' guide.
Please note: Owners must ensure that access is revoked promptly when staff or students no longer require access to the project data, for example due to leaving the University or changing roles. Owners must not rely on University card expiry for this purpose.
PIs must ensure that all access permissions are reviewed on at least an annual basis.
Automatic screen locking after a defined period of inactivity must be configured on any end-user device used to access the service, including any self-managed systems. Users should not rely solely on this to protect access to data, and should lock the screen manually or log out whenever leaving systems unattended.