GCP Console Guide

This page provides a complete guide to the Google Cloud Platform (GCP) section of the Namirasoft Credential Console. It covers each input and configuration option for securely connecting your GCP account to Namirasoft apps like Namirasoft Bill Watch. Follow this guide to set up encrypted access and manage GCP integration confidently.

What Is Google Cloud Platform (GCP)?

GCP is Google’s cloud computing service offering scalable infrastructure, machine learning, data warehousing, app hosting, and more. From startups to large enterprises, GCP enables businesses to build and run applications on Google’s infrastructure with global reliability and flexibility.

 

The Credential Management Challenge in GCP

In GCP, granting external access requires setting up service accounts, assigning roles, and managing key files. While this enables fine-grained control, it introduces risks: keys may be shared insecurely, rotated improperly, or exposed in public repositories.

 

How Namirasoft Credential Enables Secure GCP Access

Namirasoft Credential simplifies the process by letting you upload service account keys or connect via project-level APIs. All credentials are encrypted and stored securely. Once registered, you can use these GCP credentials across Namirasoft apps without re-uploading keys or reconfiguring access each time.

 

Credential usage is fully controlled by you. You can enable or disable access per app, define limits, and audit usage, all from one place.

 

Overview of GCP Credential Fields and Options

The sections below outline each field you’ll encounter during GCP credential setup. Understanding their function will help you create a reliable and secure connection between your GCP projects and Namirasoft applications.

• ID (string): This is a unique ID automatically assigned to the credential (by Namirasoft Credential) once it’s created. You don’t set this yourself; it’s used internally to reference the credential record.

• User ID (Namirasoft Account’s ID): This is the unique ID assigned to a user of the Namirasoft Account, which gives access to all Namirasoft apps. This ties the credential to a specific user (for access control and tracking). It does not directly affect authentication but is used in the backend to manage permissions and history.

• Workspace ID (Namirasoft Workspace’s ID): This refers to a workspace created in the Namirasoft Workspace app, which allows users to group projects, teams, or environments. The workspace name is displayed (not just the ID), and it links directly to the Workspace app where the workspace ID is displayed. This ensures that each credential is associated with the correct organizational context.

• GCP Credentials (JSON): This is a file in JSON format that contains everything needed to access Google Cloud Platform (GCP) programmatically. It includes a private key and metadata such as project ID, service account email, and token URI. This file allows Namirasoft to authenticate on your behalf using a specific service account without needing manual login.

• Name (String): This is a human‑friendly label you choose to identify the credential. This is required when creating a credential; helps you and your team recognize which credential is which. It has no impact on authentication itself.

• Description (String): This is an optional text field where you can explain the purpose, environment, or role of this credential. For example, you might note that it’s used for billing alerts in production or that it connects to a test project.

• Created At (DateTime): This shows the exact date and time when the credential was originally added to the Namirasoft Credential system. This value is automatically set when you create the credential and does not change over time.

• Updated At (DateTime): This shows the last time this credential was edited. Any change (like renaming it, updating the secret, or modifying the description) will update this timestamp. It helps you track when the credential was last maintained.