Dropbox Dash full demo

I'm Angie, a CSM on the Dropbox customer success team. Today, we'll follow a campaign manager, a creative director, and their IT admin as they use Dash to organize, collaborate, and protect a launch campaign.

You'll see how Dash's AI driven tools bring transparency, consistency, and security to every step from summarizing briefs with clear source citations to verifying final creative assets, sharing content securely, and enforcing policies that keep your brand safe. So let's get started.

So as campaign manager Brandi, I need to start by finding my project winter campaign brief.

Thanks to the homepage with universal search, I open my search box and type project winter campaign.

Dash is going to search across all of my connected apps to find my content. Luckily, it's smarter than I am sometimes and finds my doc through that natural language search even though the name doesn't necessarily match my search criteria.

I can see that this is the result, the content that I need by viewing the brief summary of the individual results.

I'll make a mental note for the team to change the name of the doc to be more descriptive as well so others don't have to rely on those context clues that Dash served up.

I know that my team did a lot of work on this project this week, so I wanna go ahead and summarize the status of the campaign brief to catch up.

Dash began its work pulling out key components of the doc. It has the power to summarize docs much bigger than these three pages, so my results won't take long at all. As you can see, I already have what I need. Now that I have a concise summary of the status of the brief, I messaged the creative director, Steve, and let him know that this looks good from my end.

So I'll change hats and be Steve, the creative director for the next few minutes. My role here is to define and guard the overarching creative vision, ensuring all visual and messaging elements align with the brand goals of our customer, resonate with the target audience, and are executed with high artistic quality. I've just received word from our campaign manager, Brandy, that this is good to go from her team's end. So I'll jump in and get up to speed.

My best place to start is this stack that our marketing intern created. This stack is an intelligent workspace where I can view and edit assets to jump into a project.

I'm going to challenge Dash to give me a campaign status.

I click ask Dash and then ask it to summarize the status of the project worker.

Dash is going to evaluate the items in the stack that are held in connected apps across my org. It'll run through the relevant docs of my query within the stack and provide a concise summary of my campaign status. I see the information provided is linked back to all of my original source material within the stack, ensuring full transparency and maintaining brand equity. Seeing exactly which files contributed to the summary makes it easy to trust the AI's output and keep our messaging consistent.

I see I have the option to ask some follow-up questions. Dash might even suggest a few for me. And while conversing with Dash might be helpful, I've gotten what I needed today. So I head back to my stack and let Brandy know that I'm all set.

Now, as Brandy, the campaign manager again, I receive Steve's note that he's reviewed and is up to speed. So I'll set the next meeting to gather the theme together with the client and execute next steps.

I use dash to open my calendar and set up my meeting. And since I want to grant the client secure access to my campaign resources, I decide to share this stack as part of my calendar invite. But first, I need to check the sharing permissions.

Currently, it's set to only those who are invited and that they can view it. That's perfect. The client needs to see the information, not edit it. So I move on knowing that external recipients can only see what's approved and AI summaries can help them get context fast. Secure and simple.

Let's place this link within the meeting invite.

Of course, correct our typos since it's client facing and save. After I do that, I remember that I wanted to change the name of our campaign brief to better identify association with the project.

So here I go to my search again. Recent results of course are there, so I'll search and scroll.

As my search results populate, I see multiple results again, but importantly, a few of them have this blue check mark indicating that they've been verified by our IT admin to flag across a platform for every team member to know that these are the approved versions.

So in addition to changing the name of the stock, I'll also message our IT admin, Susan, to ask that she verify the result.

So as Susan, the IT admin, I'm loving Dash. This product has given me the visibility and oversight needed to keep the company safe. I get Brandi's request to verify her doc just as I'm about to start my reporting. It's just a few clicks, so I'm happy to start there.

She tells me to search project winter campaign brief.

I search for the doc that Brandy asked me about, hover over the result, and click this checkbox.

This will mark the result as verified.

This verification step is important because it ensures everyone's aligned and prevents accidental use of outdated or unapproved files.

I go ahead and add a phrase that people will search for when they search for this doc to mark the association, and now you can see that that doc is marked verified.

Verification done. I jump into my admin console. Today, I'm gonna start with visibility, the foundation of protect and control. Most security incidents happen because no one can see where risk lives.

In each separate tool, these are scattered files, unmanaged shares, expired links. Protect and control gives me as an admin unified visibility for data access governance of connected tools like Dropbox, SharePoint, Teams, and Google Drive. As you can see, it's a lot of information.

So Dash comes with preset filters for open company links, open public links, and more.

It then comes with additional filters to fine tune the criteria so I can really narrow in on the data that I'm looking for. So let's say today, I'm interested in looking at open company links shared with people outside of our organization, within the app of Dropbox, and modified, let's say over a year ago.

These are older docs that have been shared externally and likely don't need to be out there gathering dust and allowing risk to our org. I've taken those initial thousands of results and narrowed down to under a hundred, making a large number so much more manageable for me to make decisions on.

I select all and immediately am presented with a few options.

I could either export this information to a list to potentially circulate internally to confirm that they're no longer needed to be out in the world or given the few results and last modified date, I'm much more comfortable simply stopping the sharing by removing public links.

I'll be prompted to type confirm to confirm my intention and then in just a few minutes, I've saved my company major risk of old data hanging out there in the wind. And because protecting control runs continuous discovery, these insights stay fresh, a living map of my organization's data exposure. This will be something that I check often.

Now that I've peeked behind the curtain to see a bit where the risks are, I move on to the control that protect and control offers. I was sent a note from another campaign manager who let me know the creative campaign folder was shared with dozens of external partners during production. But now that their launch is over, that access is no longer needed. Those shares would still linger though and present unnecessary exposure.

I type in project winter as the campaign manager told me is the name of the campaign.

And from the same protect and control dashboard, I can remove all external shares tied to this project.

Once I filtered for project winter and see all externally shared files, I have a choice here to either remediate individually or in bulk, selecting all and revoking access instantly. I choose to remove collaborator, select all external accounts, type confirm, and then remove.

This action ensures that all external collaborators no longer have access to this information.

That last action of removing external collaborators is a great segue to another thing I need get done this morning, complete the offboarding of the intern that joined us for fall semester.

A common gap occurs during offboarding. Access isn't fully revoked or shared content lingers in personal drives.

So my job as an admin is to off board a user, review what they touched, remove their access from content, and if requested, transfer ownership of that content to a new employee or supervisor.

This not only cleans up permissions, but ensures continuity for ongoing projects.

So I've gone in and selected the employee that I'm offboarding by clicking owner in protecting control. I have that option now to review all of the content.

This intern wasn't with us that long, so the list is short and I can put eyes on it quickly. If the list were longer, I'd consider exporting it to give myself a little bit more time to review. If the intern coordinator had asked, I could delete all the content by selecting the trash can here or if she wanted, I could add a collaborator from the team this person worked on to ensure continuity of projects. But in this case, the interim coordinator says that Jose simply needs to be removed from everything. So that's what I'll do by clicking remove collaborator.

I'll type his name and type confirm. Once I hit remove, all of the files have been unshared with Jose.

Now that I'm done in protecting control, next on my list is the review of my policies within the console.

Policies enable admins to get alerted when risk criteria are met or even remediate data automatically based on those policies.

There are fourteen built in policies for me to customize so Dash either alerts me or takes action autonomously. My CSM advised me when we signed on to Dash that customers conservatively start with alerts, once they've had a chance to review those alerts, they switch to remediation. I'm still in the alert stage. So let's look at this first one. Confidential content shared with personal accounts.

I'll click into this alert, review the content, identify that it is indeed confidential and has been shared outside of our org, and immediately stop the sharing.

Once I've done that, I fire off a note to the owner of the content to alert them to the action I've taken to protect our company's security.

Now that urgent actions are done for the day, I can turn my eyes other parts of the console like the action history and reporting.

The action history is simply an audit log for protect and control. This is helpful since my org has multiple admins and I'd like to see who's doing what to maintain oversight.

Speaking of oversight, I have an executive team who likes to hear my progress on the risk that's currently out there for our org.

To report to them, I use the reports tab to give me a bird's eye view, an aggregate view of risks across the organization through connected apps. These are the places that content is exposed externally. If I want, I can filter by app to see what risk lies per app.

I also have the stale access tab within reports, which shows me all of the content that was last modified over a year ago. Last modified is classified when permissions are changed or docs were edited last. This helps me target stale access points across older documents, ensuring that I don't change permissions on active content that needs to be externally shared.

So we hopped around a bit today from our campaign team working on and sharing out project winter to our admin team protecting what they and the rest of the company does. You got to see Dash and Protect and Control in action, diving into the concepts of collaboration, visibility into risk, leveraging automated controls to prevent exposure, and using policy based governance for safer workflows.