# Working with External Collaborators

This page describes the options for working with external collaborators:
* Sharing data through Globus
* Granting new users access to MSI systems
* Retaining access for departing group members

## Receive Data from External Users

If a collaborator outside MSI needs to send you data, they can transfer it directly to your MSI storage using Globus. The only requirement is that the collaborator has their own Globus account.

Data can be delivered to either:

- **Tier 1 storage** — use the `globus-incoming` location under your project's shared directory
    - e.g., `/projects/standard/<project name>/shared/globus-incoming`
- **Tier 2 storage** — use a `globus-incoming` prefix within your bucket
    - e.g., `s3://<bucket name>/globus-incoming`

The full workflow is described under [Receive Data from an External Globus User](../storage/transferring_data.md).

```{tip}
The collaborator does not need an MSI account to transfer data using Globus. A Globus account from their institution is sufficient.
```

## Share Data with External Users

MSI users can create a [shared collection](https://docs.globus.org/guides/tutorials/manage-files/share-files/) to grant read access to data with other users with a Globus user account.

## Grant MSI Access to an External Collaborator

If a collaborator needs to log into MSI systems (e.g., to run jobs or access software), they must first have a **Person of Interest (POI)** account created on their behalf. ([Other account types for external affiliates](https://it.umn.edu/comparison/compare-available-types-internet) do exist, but only POI accounts have sufficient security requirements to be eligible for accessing MSI.)

After the POI account is active, you can add the person to your MSI group, see steps on [MyMSI Overview](./mymsi.md).

The process for creating a POI account depends on the person’s affiliation:

### UMN-Affiliated PIs

If you are a UMN-affiliated PI, contact your departmental HR representative, who can initiate creating an “External Service Provider” (ESP) POI account. Send the following information on the user you wish to add to your HR rep:

* First and last name
* Institution Email Address
* Physical Address (office or home)
* Phone Number (office or home)
* Date of Birth

If your departmental HR rep is not familiar with the process, check [Person of Interest instructions](https://hrms.umn.edu/collection/add-person-poi?context=1346) on the HR website.

When a POI user no longer needs access, their POI relationship will need to be deactivated. Instructions for deactivating the POI designation can be found on the [Inactivating a Person of Interest / POI](https://hrms.umn.edu/resource/inactivating-person-interest-poi?context=search&surl=%252Fsearch%253Fkeywords%253DPOI%2526section%253DAll%2526sort_bef_combine%253Dsearch_api_relevance_DESC) instruction page.

### Non-UMN-Affiliated PIs

If you are not affiliated with the University of Minnesota, contact the [MSI Help Desk](https://msi.umn.edu/helpdesk) for guidance on creating POI accounts for your collaborators.

## Retaining Access After Leaving UMN

When a group member (e.g., a graduating student) leaves the University, their UMN account will normally lose VPN access and MSI eligibility. To keep them in your PI group, a **POI relationship** can be applied to their existing account.

This is handled the same way as creating a new POI account:

- **UMN-affiliated PIs** — contact your Department HR representative and follow steps 3–5 of the [Person of Interest instructions](https://hrms.umn.edu/collection/add-person-poi?context=1346). The HR representative will apply the POI relationship to the existing account rather than creating a new one.
- **Non-UMN-affiliated PIs** — contact the [MSI Help Desk](https://msi.umn.edu/helpdesk) for guidance.

## Related Resources

- {doc}`getting-started` — PI eligibility, account creation, and allocations
- {doc}`mymsi` — add and manage group members after accounts are created
- {doc}`../storage/transferring_data` — detailed Globus transfer instructions