Members

What you see on Members

The sidebar Members destination opens Team. Add Team Member accepts an email address and account role. The table lists each member's name, email, current role, role control, and Remove action. Changing the role submits immediately; removing a member requires confirmation.

Each row is one account membership. The number of rows is the current membership count, not the number of active users, project collaborators, seats used in a billing period, or people who viewed a report. One member can access several projects through the same account membership.

Role meanings

Add, change, and remove access

Use the person's account email, choose the least privilege that supports their work, and confirm the resulting row. Revisit access when responsibilities change. Removing membership blocks that account context but does not erase reports, runs, prompts, or audit evidence the person previously created.

Before removing the last responsible owner, transfer operating responsibility and verify another authorized member can manage settings and team access. Do not share user accounts as a substitute for membership.

Run a regular access review

Treat the Team table as the current authorization register for the account. Reconcile it with your customer-side joiner, mover, and leaver process, and document any temporary access with an owner and review date. PromptSpark.ai does not infer employment status, contractual authority, or whether a listed mailbox is still controlled by the intended person.

• Check members when someone joins, changes role, or leaves the customer organization.
• Give read-only access to stakeholders who only need dashboards and evidence.
• Use named accounts so generated-by fields and operational changes remain attributable.
• Remove stale membership rather than relying on a person not to sign in.
• Verify the account slug and project context when someone reports missing or unexpected access.