Can I enable two-factor authentication on Martini?

Martini does not currently expose a self-serve two-factor authentication setting. You will not see an Enable 2FA button in account settings, and the sign-in flow does not ask for authenticator-app codes or recovery codes today.

The team intends to add stronger account-security controls over time, but this help article reflects the current product. If your workspace has a security requirement that depends on 2FA, raise it through support or your enterprise contact before moving sensitive production work into the account.

Use a strong, unique password for Martini and store it in a password manager. Do not reuse passwords from other creative tools, provider dashboards, or client portals. If you signed up with a social login, secure the underlying Google or Apple account with its own 2FA setting.

Keep the email address attached to your Martini account protected, because password resets and security notifications depend on that inbox. For team work, use workspaces instead of shared logins so each person has their own account, project access can be revoked cleanly, and billing activity remains attributable.

If you see projects, generations, billing activity, or workspace membership changes you do not recognize, change your password immediately and secure the email account used for sign-in. If you use social login, review active sessions and connected devices with that identity provider.

Contact support from the help icon with the account email, approximate time of the suspicious activity, and any project or billing IDs involved. Workspace owners should also review workspace members and remove any accounts that should no longer have access.

For workspaces, the most important current control is individual membership. Do not share one Martini login across a team. Invite each collaborator separately, remove members when they leave the project, and keep workspace billing access limited to owners and admins who need it.

Enterprise teams with stricter security requirements should discuss SSO, audit, and account-security expectations during procurement. Availability depends on the contract and current product capabilities, so confirm requirements before relying on them for compliance.