Privacy & Sharing: collaborate securely - how to manage the visibility of information on Makerble
- Matt Kepple
With advanced privacy controls, Makerble lets you control access to sensitive information in your platform.
- 1 Types of privacy
- 1.1 Contacts
- 1.1.1 Access Levels
- 1.1.2 How to assign access
- 1.1.3 How To guide(s)
- 1.2 Projects
- 1.3 Stories
- 1.3.1 Access levels
- 1.3.2 How to assign access
- 1.3.3 How To guide(s)
- 1.1 Contacts
- 2 How the security layers work together
- 3 Other types of privacy
- 3.1 Albums
- 3.2 Ideas
- 3.3 Master Surveys
- 3.4 Outcomes & Progress Trackers
- 3.5 Strategy Templates
- 3.6 Organisation profiles
- 4 Learn more about how Privacy & Sharing work on Makerble
Types of privacy
The 3 main types of content that privacy apply to are
Contacts
Projects
Stories
These are explained in detail on this page
As for the other types of content that have privacy rules, scroll further down to the table that provides links to the articles that cover each of them in more depth
Contacts
Control users' access to individual Contacts
You can control the level of access that each user has to each individual contact.
Access Levels
There are 4 access levels:
Access levels are tailored to each individual user:
A user can have different access levels to different contacts
A contact can have some users with one level of access and other users who have a different level of access
| Read permitted stories about that contact | |||
|---|---|---|---|---|
Read & Write ‘Post Update Access’ | Yes | Yes | Yes | Yes |
Read Only 'Profile Access' | No | No | Yes | Yes |
Name Only ‘Headline Access’ | No | No | No | Yes |
Hidden ‘No Access’ | No | No | No | No |
How to assign access
Access can be set in two ways:
In Bulk for users with the same role:
E.g. allowing all the Project Reporters of the Farming Project to have Read Only Access to Client-A
On a user-by-user basis:
E.g. allowing User1 to have Read Only Access to Client-A while allowing User2 to have Name Only Access to Client-A
How To guide(s)
Projects
Stories
You can restrict the visibility of individual stories (i.e. case notes, attendance records and survey responses)
Access levels
There are 4 access levels
Organisation Colleagues | Story can be seen by everyone in the organisation unless Contact Privacy prevents them from seeing stories about the contact whom the story is about |
|---|---|
Project Colleagues | Story can be seen by everyone who is part of the project that the story is saved within unless Contact Privacy prevents them from seeing stories about the contact whom the story is about |
Specific Colleagues | Story can be seen by seen by the specific users that access has been granted to unless Contact Privacy prevents them from seeing stories about the contact whom the story is about |
Anonymised | This only applies to survey responses that are completed in Anonymised Mode. It means that the question responses are visible but the identity of the respondent remains hidden. |
How to assign access
Access can be set in two ways:
By default: i.e. you can set a default Access Level that applies to every story created within a particular project
E.g. in a 1:1 Counselling project you might set the default privacy of every story to be “Specific Colleagues” so that only the counsellor and their supervisor can see those notes
On a story-by-story basis:
e.g. you can set the visibility of a case study to be Organisation Colleagues so that people in the fundraising team can see it and use it in grant applications
How To guide(s)
How the security layers work together
Other types of privacy
Type of privacy | How it works |
|---|---|
Albums | Change an album's privacy level to share it with more people |
Ideas | |
Master Surveys | |
Outcomes & Progress Trackers | |
Strategy Templates | |
Organisation profiles |