Setup, navigation and lifecycle

Configure the Google Maps API key

Store the API key used for property maps, drawing, geometry, places and markers.

Audience: CRM staffPermission: AdministratorModule v1.0.0

Exact navigationAdmin Area → Settings → General Settings → Google Map API Code

Before you begin

Use an account with Administrator and confirm the intended record or setting before making a change.
Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.

What this guide covers

Store the API key used for property maps, drawing, geometry, places and markers. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.

Exact step-by-step process

Open Admin Area → Settings → General Settings → Google Map API Code.
Open the exact setting, option or record named in this guide.
Enter or select the required value; leave unrelated options unchanged.
Save the form and wait for the success response.
Reload the page or open a controlled record to confirm the stored value is being used.

Fields, choices and supported possibilities

Exact actionConfigure the Google Maps API key

Exact navigationAdmin Area → Settings → General Settings → Google Map API Code

Module version1.0.0

Access ruleAdministrator

VerificationReopen the source record and confirm the expected status, linked record, file, notification, portal visibility or financial effect.

Code-backed validations and workflow rules

The option key is real_Gogle_Map_API_Code.
Map scripts use region EG in the supplied implementation.
Restrict the key by allowed domains and required APIs.

Expected result and verification

The supported configure the google maps api key flow completes without bypassing permission or validation checks.
The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
Unexpected validation, provider or linked-record errors are investigated before retrying.

Security, privacy and operational checks

Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
Test settings and automated jobs with controlled records before production-wide use.