Cloud for remote teams: access, sharing and access management
An overview of what a remote team needs to reach shared files and systems securely, and who has access to what.
A remote team needs central user accounts, MFA, role-based permissions, a clear structure for shared files and a fixed procedure for joiners and leavers. That way everyone can reach the same data from anywhere without access getting out of hand.
Who is it for: Small teams, start-ups and freelancer collectives whose members work from changing locations and on their own or managed devices.
Which two kinds of cloud come together here?
A remote team usually uses both meanings of cloud. Files and collaboration: shared folders, documents and conversations. And infrastructure: servers, databases or management environments that the team has to log in to.
It helps to manage the two separately. Shared files involve different permissions and risks than administrators who can reach servers. This article focuses on access and sharing, with a brief look at infrastructure.
How do you arrange access?
Start with one place where identities are managed, so that you create, change and disable an account in one location. With single sign-on (SSO), an employee logs in to several services with one account. Combine that with multi-factor authentication (MFA), so that a stolen password is not enough.
- Assign permissions per role or group, not per person.
- Enforce MFA for all accounts, with extra attention for administrators.
- Limit administrator rights to a small number of people.
- Use a VPN or a similar secure connection for access to internal systems, if you have them.
How do you organise file sharing?
A clear folder structure helps avoid arguments and leaks. Create folders per team or project and decide who reads and who writes. Agree where each type of file is kept, so that nobody starts using their own copy on a laptop as the source.
Pay attention to how synchronisation behaves with a poor internet connection, with simultaneous editing and with large files. Test this in practice before choosing a service, because the experience differs per provider.
What do you arrange for joiners and leavers?
For remote teams, this is where mistakes often happen. Make a fixed list for new colleagues covering accounts, groups and MFA, and a list for departures in which access is withdrawn and devices are wiped. Record who does this, so that it does not get left undone.
- Create accounts through the central management point and assign a role.
- Have the new colleague set up MFA before the end of their first working day.
- Check every quarter who still has access and withdraw unused accounts.
- When someone leaves, remove their access to all services and hand their files over to a colleague.
Access management in key terms
| Term | Meaning | What it solves |
|---|---|---|
| SSO | One login for several services | Fewer passwords and access can be withdrawn centrally |
| MFA | Second confirmation when logging in | A stolen password is not enough |
| Role-based permissions | Permissions follow from job or group | Overview as the team grows |
| VPN | Secure connection to internal systems | Systems are not open on the internet |
| Guest account | Limited access for outsiders | Collaboration without full permissions |
Who is this less suitable for?
- Teams of one or two people: a simple shared folder with MFA is then often enough and central identity management is too heavy.
- Organisations with strict requirements for device management: managed laptops and policies require a more extensive setup than this article describes.
- Anyone who has personal data processed outside Europe: have the legal side assessed first.
Frequently asked questions
Should employees be allowed to use their own devices?
They can, but limit what they can do and ask for basic measures such as screen locks and updates. Put the policy in writing.
What is the difference between SSO and a password manager?
SSO handles the login for connected services through a single account. A password manager stores separate passwords for services that do not support SSO.
How do I prevent files from being scattered across laptops?
Agree that the shared environment is the source, and choose a service that fetches files on demand instead of copying everything locally.
