Any HERE platform user can create platform projects. Org admins and projects admins can give/remove apps, groups and users access to/from a project. The user who creates a project becomes the project admin for that project. Org admins and project admins can change project admin permissions of users, including their own. Project admins can only administer those projects for which they have admin permissions. Org admins can manage all projects, even if they haven’t been explicitly granted project admin permissions.
When working with platform projects including the creation of project resources or viewing lists of resources in a project, you will observe the project context displayed. For example:
You may change the project context to another project, opt to view all projects or simply remove the project context filter altogether depending on what resources you’re interested in.
|Maximum number of users/apps in a project||500|
|Maximum number of groups in a project||100|
|Maximum number of projects a group, user, or app can have direct access to||50|
|Maximum number of resources in a project||100|
By default, all members (inlcuding users, groups, and apps) of the project will have available access to all resources in the project. You can set up granular access to project resources through the platform and/or custom policies using the Command Line Interface (CLI). Please see the [CLI User Guide] (https://developer.here.com/documentation/open-location-platform-cli/user_guide/topics/projects-workflows.html) for details on how to set up these policies.
Any manager of an app can set or change the default project for the app from the app details page by selecting the Change default project menu option. Subsequently selecting a project in the dialog will set that project as the default project scope for the app. The manager can permit access to other projects by the app as well.
Only org and project admins can change user project permissions. Org admins can change user permissions on any project. Project admins are restricted to change user permissions for only those projects for which they have admin permissions.
While an app cannot be given org admin or group admin rights, you can make an app a project admin in the same manner as you may make a user a project admin. Groups cannot be project admins.
To add a catalog to a project, you may create a new catalog in a project, link to an existing HERE catalog from a project, or link to a catalog that's been created in another project in your org and made available for linking to your project.
When you create a catalog in a project, you may choose to make that catalog available to all or specified projects within your organization for linking with permissions that you set ("read" and/or "write"). Note that this is a two-step process. Once you make the catalog available, a member of the project that wants to link to it will need to do so as described in step 4. in the section above.
Only new pipelines can be created in a project.
Only new schemas can be associated with a project except for schemas of HERE catalogs that are linked from a project.