Control starts with access.

Learn about the product's access features and the information you can review before hiring.

Petroleum shield, glass key and permission card.

The right people, in the right context.

Access combines user, role and brand. Permissions are verified on the server and distinguish actions such as viewing analytics, publishing and replying in the inbox.

Explore the full flow
Inside metrifree
Real permission controls to set up brands, publish and approve content.
Real screen · demo dataEnlarge image ↗

Permissions per brand

Access combines user, role and brand. Permissions are verified on the server and distinguish actions such as viewing analytics, publishing and replying in the inbox.

  • System and custom roles
  • Invitations tied to brands
  • Permission checks on the backend

Credentials under control

The product stores password hashes and offers personal API tokens that can be revoked. The access session uses an HttpOnly cookie. The team should keep individual accounts and review permissions regularly.

  • Password stored as a hash
  • API token revocation
  • Individual accounts for team members

Before hiring

Request the hosting, backup, retention and incident response information that applies to the commercial offer. Certifications, SLA, SSO and two-factor authentication are not advertised on this page.

  • Assess your organization's requirements
  • Confirm terms in the proposal
  • Share questions through the sales contact

Clearer this way.

Information to help you decide your next step with context.

Visit the help center
Does API access bypass permissions?

No. Personal tokens are tied to the user, and the routes respect their permissions.

Where do I report a security problem?

Use the contact form and select Security and privacy. Avoid sending passwords, tokens or third parties' personal data in the first contact.

Your next step.

Bring your routine into a space with context.