Function Store
  • Home
  • Getting started
    • Introduction
    • Installing a function
    • Reconfiguring a function
    • Uninstalling a function
    • FAQs
  • Reference
    • Requirements
      • Assign Roles
        • User permissions
      • Link a Billing account to your project
      • Enable the APIs
    • Projects
      • How to add a project
      • How to set up a project
    • Functions
      • Benefits
      • Use cases
      • Authentication when installing
      • Runtime configuration
      • Deploying with a ZIP file
    • Policies
      • How to add a Policy
      • How to remove a Policy
    • Authentication
      • Users
      • Roles
      • Permissions
    • Secrets
      • Creating a Secret
      • Using a Secret
      • Changing the value for a Secret
      • Deactivating a Secret
  • developers
    • Overview
    • Getting Started
    • Set up
    • Workspaces
      • Create a workspace
      • Workspace boilerplate
      • Node engines
    • Writing Functions
      • Function Anatomy
      • Configuration file
      • Function Triggers
      • Environment Variables
        • Type "text"
        • Type "number"
        • Type "email"
        • Type "url"
        • Type "json"
        • Type "boolean"
        • Type "select"
        • Type "multiselect"
        • Type "firestoreDocumentPath"
        • Type "firestoreCollectionPath"
        • Type "color"
      • Documentation
    • Push/Update your functions in the cloud
    • Continuous Integration
    • Publish functions in the Marketplace
    • Emulators
      • Initialize emulators in your workspace
      • Environment variables
      • Starting emulators
      • Testing your functions in the emulator
      • Importing existing data into local emulators
        • Exporting data from Cloud Firestore to local emulator
        • Exporting user accounts from Firebase to local emulator
    • Visual Studio Code Extension
      • Installing the extension
      • Extension UI
      • Functions list
      • Creating and editing functions
      • Emulators
      • Extension settings
      • Troubleshooting
        • "Command not found" error when executing a command
  • Billing
    • Understanding Billing
  • Security
    • Security
  • Resources
    • Events and Triggers
    • Best Practices
      • How to log events in functions?
    • Document your Functions
    • Editorial guidelines
    • Our Processes
      • Use Cases Analysis
  • Use cases
    • Custom Stripe Checkout
Powered by GitBook
On this page

Was this helpful?

  1. Reference
  2. Projects

How to add a project

The following steps will guide you to assign roles to your project so that you can add it to the Project list and start installing functions with Function Store.

PreviousProjectsNextHow to set up a project

Last updated 3 years ago

Was this helpful?

Follow these steps:

1. In the GCP Console, go to the .

2. In the resource selector, select the project name to which you want to add a principal (user or service account to grant roles). You will see a menu where you can edit or delete permissions or add a principal to grant new.

3. In the Permissions tab, click the Add Principal button. In this section, you can add one or more principals and then roles to grant them access to your resources. These principals can be individuals, service accounts, or Google Groups. Note that in this case, you will be adding a service account as a principal.

4. Go to Function Store to copy the Service Account we provide you. You can find it in the Add New Projects page in the upper right corner. Paste it in the New principals box in GCP.

5. Assign Roles to the Service account. The Select a role drop-down menu, contains the roles with a short description of the permissions they grant. Assign the following roles to the service account:

  • Cloud Function Admin: Full access to functions, operations and locations.

  • Firebase Authentication Admin: Full read/write access to Firebase Authentication resources.

  • Secret Manager Admin: Full access to administer Secret Manager resources.

  • Service Account User: Run operations as the service account.

  • Service Usage Admin: Ability to enable, disable, and inspect service states, inspect operations, and consume quota and billing for a consumer project.

6. Click the Save button. Verify that the principal and the corresponding role are listed.

7. Go to Function Store, click the Check button and wait until the system verifies the permissions again.

If you already have a project in GCP that appears in the Function Store Project list but that project doesn't have the service account associated or all the required roles assigned, you can do it by setting up the project. Learn how to set up your project in the next section.

👇
Resource Manager page