Mara helps fictional teams build dependable analytics workflows. She focuses on clear access rules, useful documentation, and careful testing before changes reach a wider audience.
Fictional instructor and course, generated for this demo.
Module 1 · Set up the workspace
Read 8 minLesson 1 of 6
Map people to workspace roles
Choose roles based on tasks, not job titles.
In this lesson
Distinguish workspace roles from individual dashboard access.
Match common team tasks to an appropriate permission level.
Before inviting users, list the tasks they need to complete. A data analyst may need to create reports, while a team lead may only need to view them. Grant the narrowest access that still lets each person do their work.
Keep administrative permissions limited to people who maintain settings, users, or connections. Review access when responsibilities change.
Module 1 · Set up the workspace
Try it 10 minLesson 2 of 6
Invite users and check access
Use a repeatable review before and after adding people.
In this lesson
Prepare a user invitation with a suitable role.
Check that access matches the user's responsibilities.
Review a user invitation
1
Confirm the request
Check that the person needs access and identify the tasks they will perform.
2
Select a role
Choose the least-privileged role that supports those tasks.
3
Add resource access
Grant access to specific dashboards or data only when the workspace role does not cover the need.
4
Verify the result
Review the user's role and accessible resources after the invitation is accepted.
Saved in this browser only. Nothing is sent anywhere.
Check ownership, permissions, and expected data before connecting.
In this lesson
Identify the information needed before setting up a connection.
Explain why connection credentials should be handled carefully.
Confirm who owns a data source, which fields it contains, how often it updates, and who is allowed to connect it. Start with a test source or a limited dataset when possible.
Use the connection method approved by your organization. Do not paste passwords or access tokens into notes, dashboard descriptions, or shared documents.
Before connecting, confirm
The source owner has approved the connection.
The account has only the permissions the connection requires.
The expected fields and update schedule are documented.
Make it clear who maintains a dashboard and who can see it.
In this lesson
Identify an owner and intended audience for a dashboard.
Spot access that may be broader than necessary.
A shared dashboard should have an owner who can answer questions and coordinate changes. Its title and description should explain its purpose, intended audience, and any important limits on interpretation.
Review access when a dashboard becomes widely shared or its audience changes. Remove permissions that no longer serve a work need, following your organization's review process.
A useful dashboard review asks
Is the purpose clear from the title and description?
Is there a current owner?
Can only the intended audience view the dashboard?
Are editing permissions limited to people who maintain it?