Building Secure Research Collaboration Portals: Key Decisions

TL;DR

A research collaboration portal needs five decisions made early: who the partners are, how they sign in, how documents move through review, how partner data stays separate, and who supports the portal after launch. Make each decision in writing, then build to it. Test access before launch.

A portal gives collaborators one place for projects, documents and approvals. When it is built without clear rules, partners see too much, approvals stall, and nobody knows which version is final. Decide the rules first, then design the screens.

Decision 1: Define partners and roles

List every type of user. Typical roles are principal investigator, coordinator, partner, external reviewer and auditor. For each role, write what the user may see, change and approve. A role without a written rule will drift over time.

Decision 2: Choose how partners sign in

Partners often belong to different institutions, each with its own identity system. Decide whether to use single sign-on, email sign-in or both. Require multi-factor sign-in for every account that can see sensitive data. Agree the rules for external reviewers with your IT team.

Decision 3: Control how documents move through review

Document review needs clear states, such as draft, in review, approved and final. Each change should record who made it and when. Approvals should name the approver. A portal that shows “approved” without a name gives no assurance.

Here is a small example. A protocol passes through 3 review steps: coordinator, principal investigator and ethics reviewer. Each step has one named approver. The protocol is final only after all 3 approvals. If one approver is missing, the status stays “in review,” and the system sends a reminder.

Decision 4: Keep partner data separate

Each partner should see only the projects and documents its role allows. Test this with real accounts before launch. Check the boundary from each role, including the edge cases, such as a partner who joins a project late.

Decision 5: Agree support after launch

A portal changes after launch. Users ask for new fields, partners join and leave, and security updates arrive. Agree a support plan with response times, a change process and a monthly review.

Common mistakes

Teams often add partners before defining roles. Another common mistake is treating the portal as finished at launch. Plan the first review for one month after go-live.

Design the approval workflow

An approval workflow shows who must act next and what happens after each decision. Draw it on one page before you build it. Mark which steps are optional, which can run in parallel and which must finish in order. Give each step a deadline or a reminder, so a missing approval does not stall the study.

Decide what happens when someone is unavailable. Name a delegate for each approver, and record delegation in the system. Without a rule for absence, approvals stop whenever a person travels or takes leave.

Plan partner onboarding

Partners join at different times and with different levels of technical skill. Write a short onboarding guide with the first three tasks each role performs: signing in, finding the project and submitting a document. Test the guide with one partner before you invite the rest.

Keep onboarding records. Note who was invited, which role they hold and when they joined. When a partner leaves, the record makes removal of access straightforward.

Protect documents after they are approved

Approval does not end the need for control. Approved documents should be read-only for most users, and each change should create a new version. Keep the previous versions available for audit. Decide how long documents are kept and how they are removed at the end of a project, and write that rule into the portal’s policy.

Test with real users before launch

Run a pilot with one real project and a small group of partners. Ask them to complete their normal tasks in the portal, and watch where they stop. Most usability problems show up in the first week of a pilot, and they are cheaper to fix then than after launch. Keep a list of every issue, its owner and its status until the pilot closes.

FAQ

Can external partners sign in without an institutional account?

Yes, if your policy allows it. Use controls that your IT team approves, and limit what external accounts can see.

How do we keep partner data separate?

Set access by project and role, and test each boundary before launch. Review access whenever a partner joins or leaves.

What should a portal log?

Log sign-ins, document changes, approvals and access changes. Keep the log long enough to meet your policy.

Next step

Read our research portal development page for how we scope a portal. To discuss your partners and roles, book a discovery call.

Cloud Infrastructure for University Research Centers: A Guide

TL;DR

Plan research cloud infrastructure around four things: separate environments, role-based access, tested backups and monitoring. Decide early who runs the environment, your IT team or a partner. Choose the hosting that your data rules allow, including on-premise options where policy requires them.

Research centers run many projects, each with its own data and its own grant. Shared infrastructure with no clear rules leads to mixed data, unclear costs and unknown access. A planned environment prevents those problems and keeps each project separate.

Separate the environments

Use three environments for each application: development, testing and production. Developers work in development. Testers check releases in testing. Only approved releases reach production. Separation limits the damage from a mistake and makes changes easier to review.

Control access by role

Give each person the access their role needs. Principal investigators, coordinators, analysts and partners should not share one login. Use multi-factor sign-in for staff and partners, and review access on a set schedule. Record every change to access.

Test backups and restores

A backup you have never restored is a guess. Agree the backup schedule and retention with your IT team. Then restore a sample of data into a separate environment, check it, and record the result. Repeat the test on a fixed schedule.

Here is a worked example. A center runs 3 projects. Each project has 2 environments that hold data, so there are 6 data environments. A weekly backup for each gives 6 backups a week. If the team tests one restore per project each month, that is 3 restore tests a month. Each test checks one project’s data, so the three tests cover all 3 projects.

Monitor for failures and unusual access

Set alerts for downtime, low storage and unusual access. Send alerts to the people who can act on them. A monitoring setup that nobody reads does not protect anything.

Decide who runs it

Your IT team can run the environment, or a partner can run it for you. A third option is a partner who builds it, then hands over runbooks and trains your staff. Whichever you choose, write down who responds to alerts and who approves changes.

Plan capacity and cost together

Capacity and cost are linked. A research environment sized for peak use wastes money for most of the year. An environment sized for average use fails when a grant deadline or a large data load arrives. Plan for the usual load and a clear way to add capacity for known peaks, such as a data release or a conference deadline.

Tag each resource with its project and owner. Monthly cost reports by tag show which project uses what. Those reports make budget discussions concrete, and they show when a project has outgrown its environment.

Give partners controlled access

Research projects often include partners outside the institution. Give partners access to the specific environment and data they need, through accounts that your IT team manages. Avoid shared logins and temporary access that never expires. Review partner access when a project ends, and remove it on the same day.

Keep the runbooks current

A runbook describes how to respond to a known problem. It names the alert, the first check, the person to call and the steps to restore service. Write runbooks for the failures you expect, and test them during a planned exercise. A runbook that has never been tested is a draft.

Review the setup every year

Research needs change faster than most IT plans. Each year, review the environments, the access list and the backup schedule with the research leads. Remove environments that no project uses, and check that each project’s data still sits where the data policy requires. Record the review, so the next team knows what was decided and why.

Prepare for an audit

Auditors and data governance teams ask the same questions each time. Where is the data stored? Who can access it? How do you know the backups work? Keep the answers in one short document, with links to the access list, the backup test records and the environment diagram. Preparing this once makes each audit faster.

FAQ

Should a research center use one cloud account or many?

Use separate accounts or projects for separate grants or data owners. That keeps access and costs easy to track.

Can research data stay on-premise?

Yes, where your policy requires it. The design follows the hosting you approve, and the same principles of separation, access and backup still apply.

How often should we test restores?

Test on a fixed schedule that your team agrees, and test again after any major change.

Next step

Read our research cloud solutions page to see how we scope this work. To plan the environment for your center, book a discovery call.