Managing users
1
Open the Admin console
Navigate to Admin in the left sidebar. You land on the Users & access tab showing all organization members, their roles, and their account status.
2
Create a new member
Click Create user. Enter the new member’s full name, email address, and a temporary password (minimum 8 characters). Select their initial role and click Create account. The user can sign in immediately with the credentials you set. If your organization has email notifications configured, a welcome email is also sent automatically.
3
Assign or change roles
Click the arrow icon on any member row to open the member editor. Check or uncheck roles, update the member’s display name, and click Save access. Changes take effect on the member’s next action — they may need to refresh their browser.
4
Disable a member
In the member editor, change Account status to Disabled and save. The member loses access immediately. Disabled accounts remain in the member list so their generation history and assignments are preserved.
5
Delete a member
In the member editor, click Delete user and confirm. Deletion permanently removes the account and the organization membership record. This cannot be undone.
Role changes take effect on the member’s next action — they may need to refresh their browser for navigation changes to appear.
Roles and permissions
Each organization member is assigned one or more roles. Roles determine which parts of the platform a member can access and what actions they can take.
To customize which permissions a role carries, open the Roles tab. Select a role from the left panel and check or uncheck individual permissions. The Admin role cannot be modified — it is permanently granted every permission. Click Save permissions to apply your changes.
Managing teams
Teams group the people who own different stages of the catalog workflow. Roles control permissions; teams control operational ownership and handoff routing. Navigate to the Teams tab to see your organization’s teams. Each team card shows its workflow function (planning, generation, review, listing, or general), its members, and its designated team lead. Click Create team to define a new team. Assign a name, workflow function, and members. Designate a lead from the selected members. Teams own work items and appear as handoff recipients in Catalog Production.Configuring automation settings
The Automation tab controls scheduled email reports, planning reminders, and the Gemini event research schedule.Monthly event reports
Monthly event reports
Enable or disable the monthly event calendar email. Set the day of the month on which the report is sent (1–28). Enter comma-separated report recipient email addresses. Reports contain the full upcoming event calendar for your configured states and regions.
Event reminders
Event reminders
Enable or disable advance readiness emails for individual events. Set how many days before each event the reminder is sent (1–180 days).
State and region coverage
State and region coverage
Enter a comma-separated list of states and regions for Gemini to research — for example:
Pan-India, Rajasthan, Gujarat, Maharashtra. This controls which state festivals and regional marketplace windows appear in your Events roadmap.Organization timezone
Organization timezone
Set the timezone used for all scheduled email delivery times (e.g.,
Asia/Kolkata). This ensures reports and reminders arrive at the right local time for your team.Monthly grounded research
Monthly grounded research
Toggle whether an automatic monthly Gemini web-search pass runs to refresh and confirm event dates. When enabled, your Events roadmap stays current without manual research runs.
Configuring AI model routing
The AI routing tab lets you choose the AI providers and models used for each stage of the generation pipeline. Changes here affect all new Studio and Catalog jobs. Three routing policies are configurable:Product truth & pose planning
The vision model that analyzes your product references and builds the five-pose plan before paid image generation. Supports a primary provider and an optional fallback.
Image QA
The model that checks each generated pose against the authoritative product references. It never regenerates or deletes a paid output — it only scores and flags. Supports a primary provider and an optional fallback.
Image Generation
The model that generates the final five-pose images. GPT Image 2 is the default production model. Fallback is not supported for image generation.
API keys are never shown or stored in the AI routing screen. A provider labeled Configured means its secret is available on the server. Contact your Admin to add or rotate provider credentials.
Monitoring system health
The System tab shows health cards for each platform dependency:
A Ready badge (green) means the dependency is configured and reachable. Needs setup (amber) means a required connection or credential is missing.
The Recent audit activity table below the health cards records security, planning, and generation changes — action type, entity type and ID, and timestamp — for accountability and compliance review.