Guru's Verification engine ensures consistency, confidence, and trust in the knowledge your organization shares. Learn more.

PRIVACY / SECURITY

In this section, you can manage what Members have access to what features .

Searchability / Listing

Searchability defines who can find the container in searches and lists (e.g., who can find a project on the project tab of a Hub). Searchability does not restrict where the Container is searchable, rather who can find the container in searches. Searchability does not define whether a user can see the content of your container, it only defines whether they can find your container.

  • Public: anyone can find the Container in searches
  • Ecosystem members only: only the members in the container’s Ecosystem can find the Container in searches. Example: project P is part of community C. Hence community C is in project P ecosystem, and then all the members of community C will find project P in searches.
  • Members only: only the Project members can find the Project in searches

Content Visibility

Content visibility refers to who can see the information in in your container.

  • Public: any member on the JOGL platform can see it
  • Ecosystem members only: All the members of container’s Ecosystem can view the content of the container Example: project P is part of community C. Hence community C is in project P ecosystem, and then all the members of community C will be able to view project P content
  • Members Only: Only members of your Object can see what’s there.
  • Custom: Customize visibility for the members in your Ecosystem, i.e., for the members of each Organization, Community, and Hub affiliated to your project. If you select custom, by default the users that are not member of your ecosystem will not be able to view the content of your project/community/hubExample: project P is affiliated to community C1 and C2. The admin of project P decides to make the content of the project only visible to the members of C1 but not the members of C2.

Membership access

Membership access defines how users can become members of your Container

  • No Restriction: Users can click a “Join” button and immediately become a member.
  • On Request: Users have to send a request to the container admin before joining. Admins can define questions for users to answer to decide whether they accept the request.
  • Invite only: Users cannot join or request to join on their own. They have to be invited (link to documentation on members tab) by admins from the Members tab. They will receive a notification on JOGL if they are already a member, or an email if they need to be onboarded on JOGL.
  • Custom: For each container in your container’s Ecosystem. you can choose how the members can join your container in the Members tab. For each container, you can choose whether the members should join by invite, on request, or in an open fashion. Example: project P is member of community C and D. Project P admins would like to allow community C members to join the project on request, and members of community D to join on invite only.

Creating and adding a project

{HUB} ; {COMMUNITY}.

Projects and Communities can be created within a Hub, whereas only projects can be created in a Community. This section controls whether or not your members can do this themselves or whether admins only have the right to do this.

  • All members: All the members are able to add a project to your container
  • Admins: Only admins are able to create projects that will link to your container

Depending on the level of control you want over the growth of your ecosystem you can change this setting. You can start out with “admin only” and change to “All Members” later down the line.

Creating and adding a community

{HUB}

This functionality will appear in Hub only. This section controls whether or not your Members can do this themselves or whether admins only have right to do this. Depending on the level of control you want over the growth of your ecosystem you can change this setting.

You can start out with “admin only” and change to “All Members” later down the line.

Discussions

This section allows you to control who can post and comment on posts in the container.

  • All members: All the members are able to post in the discussions and comment on the posts
  • Admins: Only admins are able to post in the discussions and comment on the posts

Documents

This section allows you to control who can create Documents in the container.

  • All members: All the members are able to create documents
  • Admins: Only admins are able to create documents

Papers

This section allows you to control who can add Papers to the library of a container. Only for projects and communities.

  • All members: All the members are able to add papers to the library
  • Admins: Only admins are able to add papers to the library

Needs

This section allows you to control who can create needs. Needs can only be created within projects. However they can be aggregated into the communities and hubs the project is member of.

  • All members: All the members are able to create a need
  • Admins: Only admins are able to create a need

You must have Author or Collection Owner permission to create Guru Cards. Contact your team's Guru admins to use this template.