Collaborating with Other Developers

  1. Sharing a Project
    1. Sharing a project by its container inheritance
  2. Sharing and project resources
    1. Sharing and triggers
    2. Sharing and libraries
    3. Sharing and user properties

Sharing a project

This section focuses on sharing and collaboration. To learn how to share only the functionality of the project, see Managing Libraries.

Standalone projects show up in your Google Drive as a file and you can share them like any other file. For more information, see Sharing files and folders.

Container-bound projects are not visible from your Google Drive and have unique set of rules around sharing. To share a container-bound project, you simply share the parent container. For example, if you have a Spreadsheet-bound script, you would make someone an editor of the script by making them an editor of the Spreadsheet. By default, the permission and visibility settings set to container will be inherited by all the projects within that container. Another way is to share it by manually configuring the permissions and visibility for that project. For more information, see the next section.

Sharing a project by its container inheritance

  1. Open the container that has your project
  2. Click Share
  3. Configure the permissions and the visibility for the container
  4. Click Save to share the container and all the projects that it has

Sharing and project resources

Resources are entities that are associated with your project but exist independently of its code. This section explains how sharing a project affects its resources, in particular: triggers, libraries, and user properties.

Sharing and triggers

When you share a project, any installable triggers that you have created are not shared with those who have access to your project. If you plan to do any collaboration, use Script Service to create triggers programmatically, at run time. For more information, see Managing Triggers Programmatically.

Sharing and libraries

Libraries included in your project are shared with project collaborators. Though, if they do not have at least read-level access to an included library they are unable to use those libraries and will encounter an error if they attempt to do so. For more information about libraries, see Managing Libraries.

Sharing and user properties

User properties are unique to a user that created them. This means that the project collaborators are unable to see or access your user properties and you are unable to see or access theirs. Use script properties if you want to share project specific properties with the collaborators. For more information, see Using Script and User Properties.

Send feedback about...

Apps Script
Apps Script