Skip to main content

Sharing in Giraffe

Every type of content in Giraffe can be shared. Find the right sharing article for projects, spaces, layers, templates, content packs, apps, and credentials.

Written by Holly Conrad Smith

Every project, space, layer, template, content pack, app, and credential in Giraffe can be shared, and each one has its own sharing menu. Use this article to find the right one.

For the rules behind sharing, restrictive by default, permission levels, and workspace oversight, see Governance in Giraffe.

Projects

A project is where you draw, model, and analyze a site. Share a project to bring collaborators into that work. See Share Projects for the exact steps, and Project Permissions for what each access level allows.

To let a team edit the same project at the same time, see Co-Authoring. To let anyone view a project without a Giraffe account, see Publish Projects.

Spaces

A Space is a curated view of a portfolio of projects, built for stakeholders who need the big picture rather than a single site. See Share a Space for the exact steps, and Space Permissions for what each access level allows.

Space permissions and project permissions are independent. Sharing a Space with someone does not automatically give them access to the projects inside it.

Layers

A layer is a dataset in your Layer Library: a spatial file, an API connection, or data you have uploaded. Share a layer to add it to someone else's Layer Library. See Share Layers for the exact steps.

Layer governance is an Enterprise-only feature.

Templates

A template is a project nominated for reuse, so every new project starts with the right layers, usages, and analytics already configured. See What is a template? for what a template is, and Create a Template for how to designate one and choose who it is available to: yourself, a Team, or your whole workspace.

See Apply a template to start a new project from one, and Edit a template or Delete a Template to maintain one you manage.

Layouts

A layout is a saved arrangement of panels. Turn one into a template and share it with a person, a Team, or your workspace, so they get the same arrangement in their own copy. See Share layouts.

Project Attachments

A file attached to a project, like a broker's report, a zoning PDF, or a 3D model, follows that project's permission level. There is no separate sharing dialog for it. On Enterprise accounts, a project Admin can turn on Guest visibility for an individual attachment. See Project Attachments.

Files

A file in your File Library is a different thing from a project attachment, even though it shares the same underlying structure as a content pack. Share it with an individual, a Team, or your workspace from Home > Manage Account > Files. See Delete Files.

Content Packs

A content pack bundles reusable content, like layers or property definitions, into a single package. Share a content pack with an individual, a Team, or your workspace. See Share a Content Pack for the exact steps.

Apps

An app extends Giraffe with custom functionality built on the SDK. Share an app so other workspace members can add and use it in their projects. See Share an App for the exact steps.

Credentials

A credential stores an API key or token, like a tile server key, so apps and end users can connect to an outside service. Share a credential with a Team or your workspace, and separately with the apps that need it. See Share a Credential for the exact steps.

Teams and members

A Team is a group of workspace members who typically work together, like an office or a project group. Sharing something with a Team gives every current member access at once, which is faster than sharing with each person individually. See What are Teams?

See Member Permissions for the baseline access every workspace member gets, and Team Permissions for who can add or remove people from a Team.

Workspace oversight

A workspace administrator can review every project and space in the workspace, including ones that have not been shared with them, using audit mode. See How to see all projects in a workspace.

Did this answer your question?