Stitchflow
Mediafly logo

Mediafly User Management Guide

Manual workflow

How to add, remove, and manage users with operational caveats that matter in production.

UpdatedMar 11, 2026

Summary and recommendation

Mediafly user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.

Mediafly is a sales enablement platform built for large enterprises, with custom modular pricing negotiated directly through sales. SSO is available at the enterprise tier, but no native SCIM provisioning is publicly documented, meaning automated user lifecycle management is not a supported out-of-the-box capability.

Admins should expect a largely manual provisioning workflow for every app user added or removed.

Quick facts

Admin console pathUser or team administration inside the Mediafly platform; exact public help-center navigation is not documented
Admin console URLOfficial docs
SCIM availableNo
SCIM tier requiredEnterprise
SSO prerequisiteNo

User types and roles

Role Permissions Cannot do Plan required Seat cost Watch out for
Administrator Administrative users manage content permissions, user access, groups, and platform configuration. Customer platform access No public seat pricing documented. Granular permission boundaries are not publicly documented.
Standard user / presenter Standard users access sales enablement content, presentations, and assigned collateral within the Mediafly workspace. Cannot manage user accounts or system-wide configuration unless elevated. Customer platform access No public seat pricing documented. Exact role names vary across Mediafly modules and are not fully documented publicly.

Permission model

  • Model type: role-based
  • Description: Mediafly is documented in third-party reviews as using role-based access controls distinguishing at minimum between administrator and standard (viewer/presenter) roles. Granular permission details are not publicly documented.
  • Custom roles: Unknown
  • Custom roles plan: Not documented
  • Granularity: Not documented

How to add users

  1. Sign in to Mediafly with administrative access.
  2. Open the user or team administration area in the platform.
  3. Add the new user with their work email address.
  4. Assign the appropriate access level or role for the user's sales-enablement responsibilities.
  5. Confirm that the user can access the correct content libraries or groups after onboarding.

Required fields: Work email address, Role or access level

Watch out for:

  • Public step-by-step documentation is not available without customer access.
  • Some administrators report that onboarding can require customer success or support involvement.
Bulk option Availability Notes
CSV import Unknown Not documented
Domain whitelisting Unknown Automatic domain-based user add
IdP provisioning Unknown Not documented

How to remove or deactivate users

  • Can delete users: Unknown
  • Delete/deactivate behavior: Not documented
  1. Open the user's profile in the Mediafly admin area.
  2. Deactivate the user or revoke their platform access.
  3. Review any content ownership or group assignments that should be transferred before final removal.
Data impact Behavior
Owned records Not documented
Shared content Not documented
Integrations Not documented
License freed Not documented

License and seat management

Seat type Includes Cost
Platform user access Access to Mediafly sales-enablement modules, content libraries, and role-based workspace capabilities under the customer's contract. Custom pricing; not publicly disclosed.
  • Where to check usage: Not documented
  • How to identify unused seats: Not documented
  • Billing notes: Mediafly uses custom/modular pricing negotiated directly with sales. No public seat-cost or tier breakdown is available.

The cost of manual management

Because Mediafly uses modular, quote-based pricing with no published seat-cost breakdown, it is difficult to quantify the direct cost of unused licenses without engaging your customer success manager or account rep. Onboarding new users is not fully self-serve - reviewers consistently note that coordination with Mediafly support or a CSM is required.

This dependency adds friction to routine provisioning tasks and increases the operational overhead of keeping access current across every app in your stack.

What IT admins are saying

G2 and Capterra reviewers flag the admin interface as complex to navigate, particularly around content permissions and user group management. Reporting on user activity and license utilization is noted as limited within the admin console itself.

New administrators should budget extra ramp time and expect to lean on Mediafly's support resources during initial setup.

Common complaints:

  • G2 and Capterra reviewers note that the admin interface can be complex to navigate for new administrators, particularly around content permissions and user group management.
  • Some reviewers mention that onboarding new users requires coordination with Mediafly support or a customer success manager rather than being fully self-serve.
  • Reviewers note limited transparency into user activity and license utilization reporting within the admin console.

The decision

Mediafly is a reasonable choice for enterprises already invested in its sales enablement ecosystem, but IT and ops teams should go in with clear expectations: there is no documented SCIM, no public user-management API, and no self-serve admin path for provisioning at scale. Role-based access controls exist (at minimum admin vs.

viewer/presenter), but granular permission details are not publicly documented. Teams managing access across every app in a large environment will need to build manual processes or rely on SSO-gated access as a partial control.

Bottom line

Mediafly delivers strong sales enablement functionality for enterprise teams, but its user lifecycle management story is underdeveloped relative to modern IT expectations. With no SCIM, no public API, and limited self-serve admin tooling, provisioning and deprovisioning depend heavily on manual steps and vendor coordination.

Organizations with strict access governance requirements should factor this operational gap into their evaluation.

Automate Mediafly workflows without one-off scripts

Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.

Every app coverage, including apps without APIs
60+ app integrations plus browser automation for apps without APIs
IT graph reconciliation across apps and your IdP
Less than a week to launch, maintained as APIs and admin consoles change
SOC 2 Type II. ~2 hours of your team's time

UpdatedMar 11, 2026

* Details sourced from official product documentation and admin references.

Keep exploring

Related apps

6sense logo

6sense

Manual Only
AutomationNot Supported
Last updatedFeb 2026

6sense user management lives entirely in Settings > User Management (https://analytics.6sense.com/settings/user-management). The platform uses a role-based access control model scoped per product module — ABM, Sales Intelligence (SI), and Conversationa

Alkami logo

Alkami

Manual Only
AutomationNot Supported
Last updatedMar 2026

Alkami is an enterprise-only digital banking platform sold exclusively to financial institutions such as banks and credit unions. It is not a general-purpose SaaS tool, and its admin and user-management documentation is not publicly available. Independ

AmazingHiring logo

AmazingHiring

Manual Only
AutomationNot Supported
Last updatedMar 2026

AmazingHiring is a recruiter-facing sourcing platform sold on a pay-per-seat, annual billing model. There is no native SCIM support and no publicly documented IdP integration, which means every app lifecycle event — onboarding, role change, offboarding