Project sharing

Project sharing lets multiple Geoapify accounts work with the same project. Collaborators use their own accounts and do not receive access to your password or account settings.

Sharing applies to the entire project. It is not limited to an individual API key.

How project access works

A project has one owner and can have multiple collaborators.

Capability Who can perform it
View the project and its API keys Owner and collaborators
Create, restrict, or remove API keys Owner and collaborators
Review project usage statistics Owner and collaborators
Rename the project Owner
Invite or remove collaborators Owner
Manage subscriptions and billing details Owner
Transfer or delete the project Owner
Leave the project Collaborators

Collaborator access is not read-only. Changes to API keys can immediately affect applications using those keys.

Invite a collaborator

The person you want to invite must already have a registered Geoapify account.

  1. Open the project.
  2. Select Project settings.
  3. Find the Sharing section.
  4. Enter the collaborator's registered email address.
  5. Select Share.

The project appears in the collaborator's My projects list and is marked Shared with you.

If the email address is not associated with a Geoapify account, ask the person to register before sharing the project.

Work safely with collaborators

Before sharing a project, confirm that the collaborator needs access to all of its API keys and usage information.

To reduce the risk of accidental interruptions:

  • Give each API key a descriptive name.
  • Coordinate key restrictions, rotation, and removal.
  • Avoid removing a key until every dependent application has been updated.
  • Review collaborator access when team responsibilities change.
  • Use a separate project when a person should not access your other keys or project resources.

For credential-management guidance, see API keys.

Remove a collaborator

Only the project owner can remove collaborators.

  1. Open the project and select Project settings.
  2. Find the collaborator in the Sharing section.
  3. Select the remove action next to their email address.
  4. Confirm the change.

The project disappears from the collaborator's account, and they can no longer manage it through MyProjects.

Removing access does not automatically replace API keys that the collaborator previously viewed or copied. If continued use is a concern, rotate the affected keys after removing the collaborator.

Leave a shared project

If another user owns the project, open its menu in My projects and select Leave project.

Leaving removes only your access. It does not delete the project or affect its API keys, subscription, owner, or other collaborators.

The owner must share the project with you again if you need to rejoin later.

Transfer project ownership

The project owner can transfer ownership to another registered Geoapify user from Project settings.

Projects can be transferred with active or pending subscriptions. The subscription stays attached to the project; the 2Checkout customer and payment method are unchanged.

To transfer ownership:

  1. Enter the new owner's registered email address under Change owner.
  2. Select Change.
  3. Enter transfer when asked to confirm.

After the transfer:

  • The recipient becomes the project owner.
  • The recipient can manage sharing, billing, and deletion.
  • The previous owner loses access unless the new owner shares the project with them.
  • Existing API keys remain associated with the project.

Review access and API-key responsibilities with the new owner before transferring the project.

Frequently asked questions

1Who can share a project?

Only the project owner can invite or remove collaborators.

2Does the collaborator need a Geoapify account?

Yes. The email address must belong to an existing Geoapify account before the project can be shared.

3Does sharing expose my account password?

No. Collaborators sign in with their own Geoapify accounts. Sharing does not provide access to your password or personal account settings.

4Can I share only one API key?

No. Sharing provides access to the entire project and all of its API keys. Create a separate project if access needs to be isolated.

5Can I give someone read-only access?

No. MyProjects does not currently provide separate read-only and editor roles. Collaborators can manage the project's API keys, so share access only with trusted users.

6Can collaborators manage billing?

No. Only the project owner can manage subscriptions, billing details, payment methods, and invoices. Collaborators may still see the project's current plan.

7Does removing a collaborator invalidate API keys they copied?

No. Removing the collaborator prevents further access through MyProjects, but it does not change existing API-key values. Rotate affected keys if continued use is a concern.

8Can a collaborator leave without deleting the project?

Yes. Selecting Leave project removes only that collaborator's access. The project remains available to the owner and other collaborators.

9Can I transfer a project with an active subscription?

Yes, including while a subscription change is pending. Transferring project ownership does not change the 2Checkout customer or payment method. The billing customer can continue managing billing through the 2Checkout customer portal.

10What happens to API keys after an ownership transfer?

The keys remain active and associated with the project. The new owner and current collaborators can continue managing them.