Password & Security
Use the reset-password flow to protect operator access without exposing password handling inside the workspace.
Check which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
What Password & Security is for
Password & Security provides the account access recovery path for users who signed up with email and password.
The screen explains that changing a password requires setting a new one and confirming the change by email.
What each control changes
Reset password starts the password reset workflow. It should be used by the account owner or operator when login access needs to be rotated or recovered.
There are no hidden security settings on this captured screen. Teach the actual behavior: this page initiates reset, and the email confirmation completes the access change.
Operational outcome
Secure access keeps workflows, CRM records, API keys, and billing controls protected by the right user identity.
Operational playbook
Use this page to identify what the control changes, which source context it uses, who owns the result, and where to verify it.
Use the page to identify the trigger, source data, owner, visible result, and review point before changing production behavior.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Start with one workflow, message, record update, or Max task before expanding. The team should know what changed, who owns it, and how to pause or adjust it.
Troubleshooting
If the result is wrong, debug in this order: source data, permissions, connected tools, required fields, workflow logs, then any generated output used later.
When debugging, open the related CRM record, Max activity, workflow run, or integration log first. Fix the source data or rule before adding more automation.
FAQs
What does Password & Security control?
Use the reset-password flow to protect operator access without exposing password handling inside the workspace.
Who should use this page?
Workspace admins, implementation owners, and operators responsible for configuring access, account behavior, developer integrations, or the data model.
How should this page fit into onboarding?
Use it to understand the product surface, inspect real UI states, and connect the concept to daily operating workflows before configuring production behavior.
What should I verify before using this in production?
Verify ownership, permissions, source context, failure behavior, and the handoff path so teammates can trust what the system does next.