Privacy by Design
We designed Makerble with privacy in mind from the outset. Every Makerble App has privacy controls woven into the user experience to give complete control over the level of access that each user has to every piece of data.
Role-based User Access
Every organisation can manage its users from the Manage Colleagues page. Every user has an Organisation role and/or a Project role on every project they are part of.
Roles:
- Organisation Roles: Organisation Admin, Project Creator and Organisation Observer.
- Project Roles: Project Manager, Project Reporter and Project Observer.
Examples:
- Frontline staff tend to be given the Project Reporter role on the specific projects that they are part of.
- Fundraising, Strategy, Operations and Reporting colleagues tend to be Project Observers so that they have Read Only access.
Contact Privacy
Decide the level of access that each user has access to every contact in your database
Access Levels to each individual Contact:
- Post Update Access: user is allowed to post updates, e.g. notes from a 1-2-1 meeting
- Profile Access: user is allowed to read-only access to the Contact record
- Headline Access: user is allowed to see the name of the Contact and other metadata such as the projects they are part of, but not the full Contact record
- No Access: user does not have any access to the Contact
Access Levels to each individual Contact are Role-based although you can make exceptions for specific users as required.
Examples:
- Mentors, Counsellors and Advisors typically have the Project Reporter role however because they are only meant to have access to the handful of people whom they support, the General Setting for Project Reporters in the Mentoring project would be No Access to this specific Contact but the Override Setting would be used to give the Mentor Post Update Access so that they can write up their session notes.
Story Privacy
Every time you post an update about a project or contact, it is saved in your database as a story. Survey responses are saved as stories. An Organisation Admin sets the default privacy level for all stories and decides whether the authors of each story are allowed to change the privacy settings of the stories they post.
Progress Tracker Privacy
Assign particular outcomes, indicators, outputs and KPIs (Progress Trackers) to specific people. Determine whether other project colleagues have permission to see those Progress Trackers or not.
Progress Board Privacy
Progress Boards allow you to report your progress towards every outcome, indicator and metric you are tracking in your database. Choose whether you want funders, trustees or partners to have Read-only access to a particular Progress Board.
Project Privacy
Every area of work exists as its own project on Makerble. In addition to giving users Role-based Access to each project, Organisation Admins have the ability to set the privacy level of the project. This determines whether the project page is only visible to project colleagues (users who have been given Role-based Access to that project) or whether it is also visible on a Read-only basis to the wider set of Organisation Colleagues.
Album Privacy
Albums pull together progress from multiple projects. A project can be part of many albums. Album Privacy allows you to decide which users have access to that particular aggregated view of progress from multiple projects.
.png)
