Sharing your cycles is a great way to keep your stakeholders informed and make your business more transparent. When you share a cycle via Earthster with someone they will enjoy the same visuals and interactivity as you. Earthster users can find shared cycle in the process search and use it in their own cycles
NOTE: To share a cycle with your team member you just need to add them to the workspace where your cycle is. Members of the workspace can automatically see or edit a cycle according to their access rights.
Sharing cycles
To share any of your cycles first you have to issue a release. The recipients can only see the latest release. They will not see any of the changes you made since the last release.
Once you have a release go to the cycle's mini menu and click the Sharing icon.
Each cycle has its own sharing level options and groups of recipients: public and customers.
 |
|
NOTE: Your customers can not share your cycles forward to their customers within the Earthster system.
Sharing level options
With a paid subscription plan (Project, Business, Enterprise...) you can choose if you wish to share your cycles publicly or keep them private.
NOTE: Cycles created with unpaid plans (Community, Educational) are by default shared with the public with full view access including customers.
Not Shared
Private, only members of the workspace can access them
Total Impacts
Anybody with the link will be able to see the total impact of this cycle
1 level (stages)
Anybody with the link will be able to see the impacts per stages of this cycle, including cycle notes.
2 level
Anybody with the link will be able to see the impacts of this cycle up to level 2, including descriptions and processes.
All levels (full access)
Anybody with the link can see the full cycle, including descriptions and processes.
Example: Showing up to 2 levels of information.
TIP 1: If you want to share your cycle "All levels", but protect some information, you can include all the confidential information in one or more private cycles (and add those as processes).
TIP 2: Store your shared cycles in a separate workspaces. By duplicating cycles, you can have different transparency levels for each stakeholder group. You can also name them in a way that you will know which cycle is shared with someone.