{"id":1173,"date":"2025-11-12T05:10:15","date_gmt":"2025-11-12T05:10:15","guid":{"rendered":"https:\/\/cnelindia.com\/blog\/?p=1173"},"modified":"2025-11-12T05:10:15","modified_gmt":"2025-11-12T05:10:15","slug":"unified-access-bridging-freelancer-and-vendor-roles-for-a-seamless-marketplace-experience","status":"publish","type":"post","link":"https:\/\/cnelindia.com\/blog\/unified-access-bridging-freelancer-and-vendor-roles-for-a-seamless-marketplace-experience\/","title":{"rendered":"Unified Access: Bridging Freelancer and Vendor Roles for a Seamless Marketplace Experience"},"content":{"rendered":"

Project brief<\/strong>:<\/h1>\n

On a FreelanceEngine-based site, users who register as freelancers<\/em> are able to access Dokan but do not receive the full vendor capabilities\/rights. The client requested that the role freelancer<\/strong> be given all Dokan vendor rights while remaining a freelancer; and that the opposite also work \u2014 when a vendor registers they should also receive freelancer rights.<\/p>\n

Why CnEL India was the right team<\/h2>\n
    \n
  • WordPress & Marketplace expertise<\/strong> \u2014 deep experience integrating themes (FreelanceEngine) with marketplace plugins (Dokan\/WooCommerce) and resolving role\/capability mismatches safely.<\/li>\n
  • Security-first approach<\/strong> \u2014 we treat capabilities as a security boundary and perform changes so they are auditable and reversible.<\/li>\n
  • Reliable delivery<\/strong> \u2014 we provide both a production-safe implementation and a developer-friendly rollback\/testing plan.<\/li>\n
  • Clear documentation & support<\/strong> \u2014 every code change is delivered as a small plugin or mu-plugin with comments and an uninstall\/rollback path.<\/li>\n<\/ul>\n

    Challenge<\/h2>\n

    The site uses two distinct user flows and roles: freelancer<\/em> (from FreelanceEngine) and Dokan’s vendor<\/em>. By default these roles have different capabilities. The requirement was to ensure both roles have the capabilities necessary to act as a Dokan vendor and to remain functional as a freelancer \u2014 and that the mapping works both ways without elevating privileges for unexpected roles (least privilege principle).<\/p>\n

    Objectives<\/h2>\n
      \n
    1. Grant the freelancer role the capabilities required by Dokan vendors (product management, store management, order management, etc.) while preserving freelancer-specific capabilities.<\/li>\n
    2. Grant the Dokan vendor role the capabilities needed for freelancers (profile\/portfolio, access to freelance-specific pages or custom post types) so vendors may also use freelance features.<\/li>\n
    3. Make the change reversible, testable, and safe for production (no direct theme edits).<\/li>\n<\/ol>\n

      Solution overview<\/h2>\n

      CnEL India implemented a small, self-contained plugin (or mu-plugin) that:<\/p>\n

        \n
      • Reads the capability sets on both roles at runtime (so the solution adapts to Dokan \/ site variations).<\/li>\n
      • Copies Dokan vendor capabilities to the freelancer<\/code> role (if it exists) and copies freelancer capabilities to the Dokan vendor role.<\/li>\n
      • Performs the change only if the roles are present and logs the operations for audit\/rollback.<\/li>\n
      • Includes a safe uninstall\/rollback routine and a short test checklist for administrators.<\/li>\n<\/ul>\n

        Technical implementation (code)<\/h2>\n

        Install as a small plugin (recommended) or drop into wp-content\/mu-plugins\/<\/code>. The code below safely attempts to locate common Dokan role slugs and copies capabilities bi-directionally. Place in a file such as cnel-sync-dokan-freelancer.php<\/code>.<\/p>\n

        <?php\r\n\r\n<\/code><\/pre>\n
        Notes about the code<\/h3>\n
          \n
        • The plugin looks for the most common Dokan role slugs and common freelancer slugs \u2014 update the candidate arrays to match your site if you use custom slugs.<\/li>\n
        • It adds<\/em> capabilities only (non-destructive) and writes an audit log into a WordPress option (cnel_dokan_freelancer_sync_log<\/code>), so you can inspect exactly what changed before making any rollback decisions.<\/li>\n
        • If your site uses a Dokan Pro module or other plugins that add capabilities later, re-run the sync (visit ?cnel_sync=1<\/code> as an admin) so newly added caps are copied.<\/li>\n
        • We intentionally avoid removing caps automatically to prevent accidental privilege removal; if you want full reversible automation we provide a tested rollback script as part of delivery.<\/li>\n<\/ul>\n
          Testing & QA checklist (recommended)<\/h2>\n
            \n
          1. Create two staging users: one with the freelancer<\/strong> role, one with the Dokan vendor role.<\/li>\n
          2. Activate the plugin on staging and either re-register or run the sync using ?cnel_sync=1<\/code> while logged in as an admin.<\/li>\n
          3. From the freelancer account: verify vendor dashboard access, create a product, edit product, view\/manage orders, and access Dokan store settings (store name, store settings, withdrawal request page if applicable).<\/li>\n
          4. From the vendor account: verify freelancer-specific pages are accessible (profile, portfolio, or any custom freelance post types), can apply to freelance projects or create freelance listings if your theme uses them.<\/li>\n
          5. Confirm that capabilities required only for admins are NOT added to these roles (e.g., manage_options<\/code>, full plugin\/theme editing capabilities).<\/li>\n
          6. Review the log stored at cnel_dokan_freelancer_sync_log<\/code> via get_option()<\/code> or a small admin page for audit.<\/li>\n<\/ol>\n
            Security & maintenance considerations<\/h2>\n
              \n
            • Only grant the capabilities that Dokan actually needs. Our sync copies capabilities declared on the roles; review the capability list in the log and remove any capability you consider too privileged.<\/li>\n
            • Perform these changes on staging first and back up the database before running on production.<\/li>\n
            • Consider scheduling a re-sync after major plugin updates (Dokan releases new capabilities or modules).<\/li>\n
            • Track capability changes in a site-change log or within a staging\/CI process.<\/li>\n<\/ul>\n
              Deliverables provided by CnEL India<\/h2>\n
                \n
              • Small plugin file with commented code (as above) and activation\/administration instructions.<\/li>\n
              • Rollback guidance and optional rollback script (manual verification step required before removal of caps).<\/li>\n
              • Test plan and a short QA report after running on staging.<\/li>\n
              • One week of post-deployment support to resolve edge cases or adjust capability lists.<\/li>\n<\/ul>\n
                Outcome & benefits<\/h2>\n
                  \n
                • Freelancers can now use Dokan vendor features (sell products, manage store settings, manage orders) without losing freelancer functionality.<\/li>\n
                • Sellers who register can access freelancer-specific flows, enabling a flexible hybrid marketplace (products + freelance services).<\/li>\n
                • Change is auditable, reversible, and implemented without modifying theme files \u2014 safe for future updates.<\/li>\n<\/ul>\n
                  Favourable client review<\/h2>\n
                  \u201cCnEL India delivered exactly what we needed: a secure, tested solution that allowed our freelancers to become full Dokan sellers while keeping their freelancer features intact. The team provided clear documentation, a neat plugin we could install on staging, and step-by-step testing guidance. Deployment on production was smooth and backed by responsive support. Highly recommended.\u201d<\/p>\n