How to manage projects

A project is a container for securely managing HERE platform resources. Projects let you manage which users, apps, and groups can access the resources created or linked to the project.

Why use projects?

Some benefits of using projects include:

• Collaboration: Streamline your workflows by only using resources that matter to your team, and help other teams by sharing useful resources with them in a controlled manner (bidirectional trust).
• Workflow management: Accommodate different access requirements for development, test, and production environments.
• Access management: Control access to individual resources by assigning project policies for users, groups, or apps. For more information, see Project policy.
• Cost tracking: Track resource usage by project in the platform Usage report so you can closely control costs.

📘

Note

When you work with projects, the project context is visible in the portal. For example:

You can change the project context to another project, switch to viewing all projects, or simply remove the project context filter altogether.

How to create a project

To create a project:

1. Sign in to the HERE platform.
2. Select the Projects Manager from the launcher.
3. Click Create new project.
4. Enter a name for the project (project names don't have to be unique).
5. Enter a project ID. Project IDs must be unique within an org, and can't change for the lifetime of the org. Project IDs must be 4-16 characters in length.
6. Enter an optional description.
7. Click Save.

After you create a new project, you can find all your projects on the Project Manager page. By default, you have admin rights to the project you created. You can also grant admin rights to other users and apps.

On the project management page, you can also find a newly created HERE Resource Name (HRN) identifier. An HRN is a unique identifier of catalog, schema, pipeline resources, platform projects, and apps.

The HRN generates automatically by the HERE platform when you create a resource, project, and app, and you can't modify it. You can use the HRN to specify the project scope for requests to the HERE platform (which is recommended for usage tracking).

For additional information, see Create a token signature and Billing tags for projects.

📘

Note

Org admins can manage all projects, even if they haven’t been explicitly granted project admin permissions.

Manage access to a project

Managing access includes granting and revoking access, configuring project policies, setting a default project for an app, and managing and revoking project administration, such as roles and permissions.

Grant access to a project

To grant access to a project, follow these steps:

1. Sign in to the HERE platform.
2. In the Projects Manager, select the project for which to give a user, group, or an app access. Select the Access and permissions tab to view a list of users, groups, and apps with access to the project.
3. Click Grant access.
4. Select whether you want to search by existing groups, or existing users and apps.
5. Enter the name in the search field to find the desired user, group, or app by name.
6. Select the desired name and click Grant access. The name is now listed.
7. Alternatively, you can use the links on the Grant access to a project window to create new users, groups, or apps in the Access Manager. When creating an app this way, the default project for the app is automatically set to the project in which you were working, and is optionally set to only allow access in the default project.

📘

Note

By default, all members of the project (including users, groups, and apps) have access to all resources in the project. You can set up granular access to project resources through platform policies and custom policies, using the Command Line Interface (CLI). For more information, see Projects workflows in the Command Line Interface User Guide.

Remove access to a project

To remove access to a project, follow these steps:

1. Sign in to the HERE platform.
2. In the Projects Manager, select the project from which to remove access for a user, group, or an app. Select the Access and permissions tab to view a list of users, groups, and apps with access to the project.
3. Click the ellipsis menu to remove the user, group, or app access to the project. A Remove from project button appears.
4. On the popup dialog, click Remove to confirm.

Project policies

A project policy is a set of rules or permissions you can apply to identities within a project to manage access and actions on resources. It includes configurations such as an identifier, name, description, and a list of permissions specifying allowed actions on resources or resource types within the context of the project.

IAM enables you to set up granular access to the project resources through project policies. For more information, see Project Policy.

Set a default project for an app

App managers can specify a default project for the app during or after the creation of the app. This means that requests from this app connect to the specified project by default, allowing you to track usage by this app at a project level.

When creating an app from a project in the Projects Manager, the system automatically sets the default project to the project in which you are working. When creating an app from the Access Manager, you can optionally select a project in the "DEFAULT ACCESS TO A PROJECT" field.

To set the default project for the app after it's created, go to the app details page in the Access Manager, select the Edit app menu option, and select a project in the DEFAULT ACCESS TO A PROJECT field. Select the None option if you have multiple apps.

You can also set the app to only request resources from the default project by selecting the Allow access in only in this project checkbox during or after app creation. HERE recommends this setting for apps using API keys because it helps secure the use of your API keys. It also allows you to track usage by project for an app using an API key.

📘

Note

You can't add apps set to only request resources in the scope of the default project, to groups. This is to prevent the app from inadvertently becoming a member of other projects (through its group membership) where it won't work since it's restricted to use in another project.

If you need to use an app across multiple projects, for example, to coordinate CI/CD processes, HERE recommends you use OAuth 2.0 tokens and set the project scope as needed when requesting the token.

Manage (assign or revoke) project administration

Only org admins and project admins can change identity (user or app) project permissions. Org admins can change identity (user or app) permissions for any project. Project admins can change identity (user or app) permissions only on those projects for which they have admin permissions.

To revoke a project admin, follow these steps:

1. Sign in to the HERE platform.
2. Click on the Access and Permissions tab of your project to view a list of users, apps and groups with access to the project.
3. Click the ellipsis menu to change project admin permissions for a user or an app. A Make project admin button appears if the user or app isn't already an admin. A Revoke project admin button appears if the user or app is an admin. Clicking the appropriate button immediately changes the project admin permissions for the user or app.

Manage resources in a project

From within a platform project you can create, delete, link, and share resources in a controlled manner. This is the recommended way to manage access to resources. The following sections provide instructions on how to manage project resources by resource type.

Catalogs

You can add or remove a catalog to a project, share, turn off sharing for a catalog, or change permissions for a catalog.

Add a catalog to a project

There are multiple ways to add a catalog to a project. You can create a new catalog in a project, link to an existing HERE catalog from a project, or link to a catalog that's created in another project in your org and made available to link, designated as "shared," to your project.

To add a catalog to a project, follow these steps:

1. Sign in to the HERE platform.
2. In the Projects Manager, select the project for which to add a catalog and select the Resources tab.
3. Click Add catalog and choose one of the following options:
   • Link a catalog: Choose this option to add an existing catalog to the project. You view a list of catalogs provided by HERE, as well as catalogs from other projects within your organization. Click the Link button for the desired catalog. If a choice is available, select the permissions for the catalog, for example, "read" and "write." The catalog then appears in your list of project catalogs with a link icon next to the catalog name and the linked permissions.
   • Create a new catalog: Choose this option to create a new catalog and add it to the project. For more information on creating catalogs, see the Data API.

Remove a catalog from a project

To remove a catalog from a project, follow these steps:

1. Sign in to the HERE platform.
2. In the Projects Manager, select the project from which to remove a catalog, and select the Resources tab.
3. Click on the ellipsis and select Unlink.

Share a catalog

Sharing a catalog makes it available to link to other projects in your organization. You may choose to make the catalog available to all, or specified projects within your organization with permissions that you set ("read" and/or "write").

To share a catalog, follow these steps:

1. Sign in to the HERE platform.
2. In the Projects Manager, select the project which contains the catalog to share with one or more projects in your organization.
3. Click the ellipsis menu next to the catalog you would like to share and select Set catalog availability.
4. Specify the project in which to share the catalog, or choose Make available to all projects in your organization.
5. Specify the permissions for the catalog to share: read and/or write.
6. Click Set.

The previous steps describe this capability in the context of Projects Manager. This capability is also accessible to users with manage access to a catalog from the catalog detail page in the Data section of the portal. Additionally, users with manage access permission to a catalog can unlink that catalog from a project, from the Availability tab of the catalog detail page in the Data section of the portal. The steps for all of these actions are in the Data API Developer Guide.

Turn off sharing for a catalog

To make a catalog unavailable to link to projects, follow these steps:

1. Sign in to the HERE platform.
2. In the Projects Manager, select the project which contains the catalog to modify.
3. Click the ellipsis menu next to the catalog and select Set catalog availability.
4. Deselect Make available to all projects in your organization.
5. Click Set.

📘

Note

Disabling catalog sharing doesn't unlink it from currently linked projects. A user with manage access permission to the catalog can unlink it from a project from the Availability tab of the catalog detail page, in the Data section of the portal, as described in the Data API Developer Guide.

Change permissions to a shared catalog

To change the available permissions to a catalog after you have shared it, follow these steps:

1. Sign in to the HERE platform.
2. In the Projects Manager, select the project which contains the catalog to modify.
3. Click the ellipsis menu next to the catalog and select Set catalog availability.
4. Change the permissions by selecting the desired check boxes.
5. Click Set.

📘

Note

Changing a catalog's permissions in a project doesn't change the permissions of the catalog for any project already linked to the catalog.

Schemas

Add a schema to a project

There are multiple ways to add a schema to a project. You can create a new schema in a project, link to an existing HERE schema from a project, or link to a schema that's created in another project in your org and made available to link, designated as "shared," to your project. Linking schemas, whether user or HERE created, is currently only supported through the CLI.

To create a new schema in a project, you must associate the schema with the project when you create the schema's Maven project using the HERE Data SDK for Java and Scala. To associate the schema with a project, specify the project's HERE resource number (HRN) in the here.token.scope property in your local ~/.here/credentials.properties file before you deploy the Maven project. Then, when you deploy the Maven project containing the schema, the schema deployment plugins create the schema in the specified HERE platform project. For more information, see Create and Extend Schemas.

After you deploy the schema, it lists in the project on the Resources tab, in the Schemas section.

📘

Note

Schemas associated with catalogs linked to a project aren't listed in the Schemas section of the Resources tab. You can view them by navigating to the Data section of the portal, selecting Schemas, and then selecting the project from the drop down menu in the top right corner of the window.

To link a schema that's been shared to a project, see the CLI documentation.

Share a schema (CLI-only functionality)

Sharing a schema makes it available to link to other projects in your organization. You may choose to make the schema available to all or specified projects within your organization with "read" permissions. For more information, see the CLI documentation.

Once you share a schema, an app sharing the project, can link to the schema. For more information, see the CLI documentation.

Pipelines

Add a pipeline to a project

To add a pipeline to a project, you must create the pipeline in that project. You can't link an existing pipeline to a project.

To create a new pipeline and add it to a project, follow these steps:

1. Sign in to the HERE platform.
2. In the Projects Manager, select the project to which you want to add a pipeline.
3. On the Resources tab, click Pipelines.
4. Click Create new pipeline.
5. Complete all of the required fields. Ensure that you leave the Create pipeline in a project option selected, and verify that the Home Project field matches the name of the project which created the pipeline. For more information, see Using the Web Portal for Pipelines in the Pipeline Developer Guide.
6. Click Save Version.

Services

Add a service to a project

To add a HERE service, such as HERE Routing or HERE Search - Forward Geocoder, link it to your project by following these steps:

1. Sign in to the HERE platform.
2. In the Projects Manager, select the project in which to add a service.
3. On the Resources tab, click Services.
4. Click Link a service.
5. Click the Link button for a HERE service to add to the project. The selected service now appears in the Services list in the Resources tab.

Remove a service from a project

To remove a HERE service, such as HERE Routing or HERE Search - Forward Geocoder, from a project, follow these steps:

1. Sign in to the HERE platform.
2. In the Projects Manager, select a project.
3. On the Resources tab, click Services.
4. Click the ellipsis menu to the right of the service to remove, and select Unlink.

Delete a project

To delete a project, you must first delete any resources created in the project. Deleting resources in a project could have an impact on all the users, apps, and groups that are members of the project, as well as members of other projects that have linked to resources in your project, so please proceed with caution.

Once you've deleted the project resources, delete your project by following these steps:

1. Sign in to the HERE platform.
2. In the Projects Manager, select the project.
3. Click the More button, then select Delete project.

📘

Note

To delete a project, verify that your role is either ProjectAdmin or OrgAdmin. Other roles do not have permission to delete a project.

Once you delete a project, the project ID of the deleted project cannot be reused for a new project.

Project limits

The maximum project limits are in the following table:

Projects and the CLI

You can also use the CLI to work with projects. For more information, see the HERE OLP CLI - User Guide.