Project sharing
  • 15 Nov 2022
  • 1 Minute to read
  • Dark
  • PDF

Project sharing

  • Dark
  • PDF

Article Summary

The content on this page is outdated. We have moved all Business Technology Platform (BTP) documentation to the Help Portal.

To find the latest version of the following article, click here.

Don't forget to update your bookmarks!


Project sharing allows you to add members to your SAP AppGyver project and enables collaborative editing. Each member is entitled to a user role that permits only a certain set of actions within the project.

User roles

  • Viewer: Read-only actions, such as viewing and deploying.
  • Developer: Edit, deploy, release, manage dependencies in a project, and publish to the library.
  • Administrator: Complete access, including editing, sharing, and deleting a project.

A higher user role includes all permissions of the preceding ones.

Sharing your project

Project sharing is done via Application Development Lobby.

  1. Locate an existing AppGyver application you would like to share and click on "Me" under the 'Members' column, or 'Manage Members' in the three dots menu:

Project Sharing

  1. In the pop-up window:
    1. Enter an email of the user you are sharing the project with.
    2. Choose a user role from the dropdown.
    3. Click 'Add' to enter the user to the list.
      1. If necessary, add more users.
    4. Click 'Save' to share the project with entered users.

Configuring users and user roles

Collaborative editing

After sharing the project, members with roles 'Developer' and 'Administrator' can start making changes to the application. Current simultaneous editing follows the following ruleset:

  1. Unsaved changes are continuously applied on top of the latest saved version by another user. In other words, non-conflicting changes will be immediately reflected for all members, without intervening with their work.
  2. Editing the same parts of the project, e.g., page name or component style class, will cause a conflict. Conflicts are resolved by reloading the page, where conflicting changes are discarded. Note that conflicts are resolved in favor of the latest saved version.
  3. User profile coloring in the top bar reflects the current state of the user. Grey implies no unsaved changes, while orange tells that the user is currently editing the project.

It is of best practice to save the application frequently to avoid conflicts and make sure that all developers have the latest version.

Was this article helpful?

What's Next