Set permissions once for every Delalify product

Set each colleague's access once in Teams, since People, Channels, and OneCloud check that role whenever the colleague opens a contact record, a campaign, or a drive. When you edit the role, each of those products applies the new permissions on its next request.

One dashboard for all permissions

Teams is the one place where you set what each colleague can open across the Delalify suite. When you add someone to a project or move them into another role, People, Channels, and OneCloud grant what their new role allows and withdraw what it leaves out. Every Delalify product applies the one permission list that Teams holds.

Follow one colleague from the invitation that you send to the day that their access ends

These steps follow one colleague through Teams, from the invitation that brings them into your workspace to the deactivation that closes their access.

Control access across the entire suite

User membership and role assignment illustration

A new hire can open Delalify only once an administrator creates their account, so a queue of IT tickets will delay their first day. The administrator will also need to know each product well enough to choose the right permissions, because a role that is too broad can let the hire into records that their job never needs, while a role that is too narrow can keep them from doing the job.

When you invite a colleague by email, Teams sends them a link for setting up their own account. Admin, Editor, and Viewer each come with default permissions across the whole suite, so you can usually set up a new hire with one choice from that list. Where no standard role fits the job, you can build a role from individual permissions, such as a role with access to the finance drive in OneCloud alone. Teams also lists each invitation that is still pending, so you can see who has yet to join and send them the link again.

Directory sync and single sign-on illustration

Your identity provider already holds a record for every employee, yet without a sync an administrator will have to create each of those people again in every application. Every extra account gives a colleague another password to keep track of, so your help desk will receive a reset request whenever someone forgets one. An account outside your directory can also stay active after the person who owns it leaves.

Teams connects to Microsoft Entra ID, Google Workspace, and other SCIM providers, and then gives a Delalify account to each person in your directory. Your colleagues sign in at that provider, so Delalify keeps no separate password for them to forget. When HR removes someone from the directory, Teams closes their Teams membership at the next sync, which ends their access to People, Channels, and OneCloud.

When HR adds someone to your directory, an administrator will still have to open each application and repeat the same setup for that person, so the new hire will wait for that work before they can send a message or open a file. A departure will need the same round of visits, since each account stays open until an administrator closes it.

Map each directory group to a Teams role once: the marketing group to Editor, the finance group to Viewer, and the IT group to Admin. When HR then adds someone to the marketing group, Teams gives them a Delalify Teams membership as an Editor at the next sync. When HR moves that person out of the group, Teams withdraws the Editor role at the following sync. If HR removes them from the directory altogether, Teams deactivates the membership at that sync.

Activity monitoring and audit logs illustration

When a colleague holds a permission beyond their job, your security lead's first question will be who granted it and when. To answer it, someone will have to collect the logs from each application separately, if each application records permission changes in the first place. When an auditor asks whether your access records agree with your HR records, a colleague will also have to compare the two lists by hand.

Teams records every sign-in, every permission change, and every record or file that someone opens across the whole suite. You can narrow that history to one person or one date range before you export it for a compliance review. Teams also notifies you when a colleague takes on a wider role than they held before. For the review itself, Teams reports current access beside directory status, so you can show an auditor that the two agree.

Someone who leaves keeps working credentials until an administrator revokes them in each product that they use. If an administrator deletes the account, the team will lose the files and conversations that the person created. A contractor can also keep every permission that you grant in their first week long after their project ends.

When you deactivate a person in Teams, Teams closes their access to People, Channels, and OneCloud in a single action. The files and conversations that they create stay under their name, where a workspace admin can open them and pass them to whoever takes over. You can also give a contractor an invitation with an end date on it, so Teams closes their account on the day that their booking ends. After Teams closes the account, it keeps the log of everything that the person opened, so you can trace the whole engagement later.

1

Permissions dashboard

Instant

Access revocation

0

Separate admin panels

What one permission list changes for your administrator

One edit for every product

People, Channels, and OneCloud each check a colleague's role in Teams before they open anything for that person, so a role that you grant in Teams applies in all of them at once. To review what a colleague can reach, read their role in Teams.

Access ends when the employment does

Teams ends a former employee's access at the first sync after HR takes them out of your directory. If they are still signed in at that point, Teams signs them out as part of the same deactivation.

A record that an auditor can follow

Teams records the name of the person who makes each permission change and the time of the change, so an auditor who asks who widened a role can find the entry with the answer. Because Teams takes each role from your directory groups, the access list that you hand over matches the HR list beside it.

The sign-in that your team already has

Your colleagues sign in to Delalify with the same account that they use for the rest of your systems, so your provider's rules on password strength and second factors apply to Delalify too. If every colleague signs in that way, the one credential that each of them holds is the one that your provider issues.

How organizations manage access with Teams

A logistics company brings on warehouse crews each peak season

The operations lead at Harbourline Freight gives every seasonal warehouse hire one shift-supervisor role, which holds the permissions for the People contacts and the Channels dispatch threads that a shift uses. As a 40-person crew forms for the holiday rush, the lead gives each new worker that same role. When the season ends, the lead deactivates the temporary accounts in a single bulk action.

Result

Each seasonal worker holds the same access as the rest of their crew, because every one of them holds the shift-supervisor role. At the end of the season, the lead closes every temporary account with one bulk deactivation, so the lead starts the next peak with the accounts of the permanent staff alone.

A logistics company brings on warehouse crews each peak season

Day one for a new regional sales hire

A sales manager invites a new regional rep by email, adds them to the regional team, and gives them the Editor role. That role holds the permissions for the territory records in People, the regional campaign tools in Channels, and the shared deal files in OneCloud. The rep sets up their account from the join link and starts work that morning.

Result

The new rep can open their territory's records on their first morning, because Teams grants that access along with the role. The manager adds no separate grants, so the rep can open the records for their own region alone.

A healthcare organization keeps patient data within HIPAA rules

The compliance team at a healthcare organization requires each departing staff member's access to patient data to end with their employment. When HR records a termination in the identity provider, Teams deactivates that person's account at the next sync, which closes their access to the contact records in People, the conversations in Channels, and the files in OneCloud. Teams logs each time a staff member opens patient data, with their name and the time.

Result

When the annual HIPAA auditor asks who opened patient data, the compliance team answers from that log. The team exports it for the auditor in a standard format, so the auditor can review the access to People, Channels, and OneCloud in one file.

A healthcare organization keeps patient data within HIPAA rules

An agency moves freelancers between client accounts

A creative studio brings freelancers on and off projects every few weeks. The studio lead gives each freelancer a custom role with access to the People contacts and the OneCloud files of the one client that they are booked on. When a booking ends, the lead either deactivates the freelancer or edits their role for the next client, which Teams applies on the next request.

Result

Each freelancer can open the records of their booked client alone, so the studio's client accounts stay apart. The lead moves a freelancer to the next project by editing one role, because Teams applies that edit in every product that the freelancer uses.

An agency moves freelancers between client accounts

A school district manages roles for every product from one screen

When each product keeps its own permissions, the IT team at a school district will have to make every role change once in each product and then check that the products agree. With Teams, the district's IT team manages the roles for People, Channels, and OneCloud from one screen. When IT promotes a teacher to head of department, Teams widens their access in every product with that one edit.

Result

Each role change takes one edit in Teams, which every product applies on its next request. When IT reviews who can do what across the district, the team reads one list of roles in Teams.

A school district manages roles for every product from one screen

Common questions about Teams

Set each colleague's access in one place

People, Channels, and OneCloud apply the role that you give each colleague in Teams, while the activity log records what each person opens.