One file store for your whole workspace

OneCloud stores every file beside the contact, the project, or the team that it belongs to, while Delalify Teams holds the list of colleagues who may open it.

Every document filed under the contact that it concerns

When you upload a contract, a recording, or a policy document into OneCloud, you can attach it to the contact in People whom it concerns. When you open that contact's profile, People shows those attachments on the record itself. OneCloud can also list the files for a whole group or tag from People at once. Delalify Teams holds the permissions that OneCloud checks before it opens any file, so each colleague can open the files that their role allows. When a colleague opens a contact's record next year, they find the file that you attach today, along with its versions and its access log.

Follow one contract from the upload to the audit log

OneCloud stores each file with the history of its earlier versions, the log of who opens it, and the contact in People that it belongs to. The steps below follow one contract from its upload into a drive to the log that an auditor reads.

Every file linked, every access logged

File storage with version control illustration

The same document can exist as a desktop copy, an email attachment, and a file in another service, so a colleague who opens one of them will have to ask which copy holds the current text. Because anyone can edit any of those copies on its own, whoever assembles the final wording will have to reconcile three documents by hand.

Upload documents, images, and media into folders that you name after your teams or your projects. When you save a newer draft, OneCloud stores it as the current version and keeps the one that it replaces in the file's history. OneCloud also indexes the text inside each document, so you can search on a phrase that you remember and read the passage that matches it. You can see how much space each team uses as well, so you can hold a team to the allowance that you agree with them.

If a folder holds the signed contract while People holds the profile of the person who signed it, the colleague who filed both may be the one person who knows that the two are connected. Anyone else who looks for everything that your organization holds on one person will have to search each system in turn.

Attach a file to a contact in People as you upload it, or later from the file itself. People then lists the contracts, proposals, and correspondence that your colleagues attach on that contact's profile, newest first. Channels records every attachment that it sends on the contact's thread, so People lists those documents beside the ones that your colleagues upload themselves.

Team-owned shared drives illustration

If one colleague owns the folder that holds a project's files, the team will have to ask your IT staff to reopen it once that person leaves, so everyone else on the project will wait on that request. If you give the whole team the same level of access, an intern who needs to read the files can also delete them, while a partner who owes you a deliverable can read the files but cannot add to them.

Your team owns a Shared Drive together, so the files stay in place when one member moves to another project. Give each person or each Teams group the viewer, editor, or manager role that matches their part in the work. You can set the drive up yourself or switch storage on for a People group, in which case OneCloud creates the drive and names it after the group. Either way, your colleagues open it under the roles that you give them in Delalify Teams. For someone outside your organization, send a link with an expiry date, a password, or both.

Access tracking and audit trails illustration

When an auditor asks who opened a sensitive document last quarter, the answer will need a person's name and a time. Your security lead can ask the same question about a file that leaves the organization before an incident. If each application keeps a record of its own, a colleague will have to read through all of them before they can answer either question.

OneCloud keeps a history for each file and each Shared Drive, which records every view, download, share, and permission change as a separate entry. You can limit that history to one person or one date range, then export it for whoever asks. OneCloud keeps those entries after the file moves and after the person leaves, so a colleague who investigates a year later can still find them.

A new project team will need a drive for its files from its first day. As the team changes, somebody will then have to add and remove people on that drive, which usually means more work for whoever created it.

When you switch storage on for a People group, OneCloud creates a Shared Drive with the group's name and a link back to the group, so anyone who opens the drive can see which contacts it concerns. You then grant access in Delalify Teams, either to named workspace members or to a group from your directory. If HR later moves someone out of that directory group, Teams withdraws their access to the drive at the next sync.

Every

File version kept

0

Separate permission lists to maintain

Full-text

Content search

Why your team keeps its files in OneCloud

One profile, every file attached to it

People lists each file that you attach to a contact on that contact's profile, and each file that you attach to a group or a tag on that group or tag. A colleague who prepares for a renewal call can therefore open the contract, the last proposal, and the meeting notes from one screen.

Links that you can close after you send them

When you send a file through Channels to someone outside your organization, you can put a password, an expiry date, or both on the link. You can also withdraw the link before that date if the work finishes early. Once the link expires or you withdraw it, it stops opening for everyone who has it, including anyone whom the recipient forwards it to.

Evidence that a compliance review can use

The log records what each colleague does to a file and when, so you can export the period that the reviewer asks about. OneCloud also deletes files on the retention schedule that you set and stores them in the region that you choose, so the policy that you show an auditor describes what OneCloud does with your files.

Your organization keeps the drive when someone leaves

Your organization owns each Shared Drive, so the colleague who takes over a departing member's work opens those files under their own account. Once you give that person a role on the drive in Teams, they can read what their predecessor left, along with the version history behind each document.

How organizations keep their files in OneCloud

An insurance brokerage files each policy under its client

A broker uploads the policy schedule, the endorsements, and the renewal quote, then attaches each one to the policyholder's contact in Delalify People. The account team reads every document from that profile, while the brokerage gives that team alone access to the premium terms through its roles in Teams. When an underwriter asks for supporting paperwork, the broker sends a link and withdraws it once the underwriting finishes.

Result

On the renewal call, the broker reads the current schedule from the policyholder's profile and names the endorsement that changed it. If a regulator asks which terms applied on a given date, the broker opens the schedule as it stood then from its version history, along with the log of everyone who opened it.

An insurance brokerage files each policy under its client

Grant reports pile up across a nonprofit's chapters

A national nonprofit switches storage on for the People group of each regional chapter, so each chapter has a Shared Drive named after it. Field staff upload receipts, narrative reports, and budget spreadsheets into their chapter's drive, where OneCloud keeps every draft as a version. A program officer can open any chapter's drive as a member of the program team's group in Teams.

Result

Headquarters compiles the annual grant report from the chapter drives, using the version that each chapter marks as final. When a program officer starts in the middle of a grant cycle, the chapter drives open for them as soon as an administrator adds them to the program team's group in Teams.

Grant reports pile up across a nonprofit's chapters

A registrar files each applicant's documents on their record

As transcripts, recommendation letters, and test scores come in, a university registrar attaches each one to the applicant's contact record. Only the review committee for that applicant holds a Teams role with access to those documents, while OneCloud logs every view or download for the accreditation team. OneCloud deletes each application on the retention schedule that the registrar sets.

Result

A reviewer opens one applicant record and finds the transcript, the letters, and the scores already filed under it, so the committee spends its meeting on the decision. When the accreditation team asks who read which application, the registrar exports the log for the period that they name.

A registrar files each applicant's documents on their record

Three regional offices share one brand library

A franchise operator keeps the logos, the ad templates, and the store-layout guides in one Shared Drive that the brand team owns, so all three regional offices work from the same set. When a designer uploads a new template, OneCloud makes it the current version and keeps last quarter's in the history behind it. A regional manager shares the templates with each franchisee through a link with a password and an expiry date that the manager sets.

Result

A store manager who opens the drive downloads the logo that the brand team approves, because OneCloud shows the current version first. Each link expires on the date that the regional manager sets, so a franchisee who needs the artwork after a campaign ends will ask the regional manager for a new link.

Three regional offices share one brand library

An engineer settles a production-line dispute from the version history

A robotics assembler keeps its work instructions and machine-setup sheets in OneCloud, where each sheet's history holds every revision that the plant uploads. When the crew on one line builds to the wrong torque spec, the process engineer opens that history and compares the current sheet with the revision before it. The engineer then restores the revision that the line should follow. The log also names whoever saved the wrong revision, along with the time of the save.

Result

The crew restarts the line on the same shift, because the engineer restores the correct sheet from the file's own history. Whoever reviews the incident later can read the same history to see which revision the plant worked from at each point of the shift.

Common questions about OneCloud

Keep each file beside the contact that it concerns

Attach contracts and proposals to contacts in People, send them through Channels, and grant access to them in Teams, all from one stored copy in OneCloud.