Nederlands 
English (UK) 
Русский 
العربية 
日本語 
한국어 
Magyar 
Türkçe 
Español 
Čeština 
Svenska 
Português 
Ελληνικά 
Suomi 
Română 
Italiano 
Français 
Polski 
Українська 
Deutsch 
简体中文 
Slovenčina 
Recommendation: autorisés third parties as partners in Meta Business Suite, then assign a spécifique role for each case and bound the total scope. Utilisez explicit permissions to keep the access under control, and voir activity in the audit logs. Define the bestemming of assets and base sharing on the minimum requirement; keep the process complète.
étape 1: Connecter to Meta Business Suite, go to Settings, and cliquez “Add People” under the Partners tab. In the listes of people, choose the third party and click to confirm. Set the access bestemming and select a spécifique scope. If needed, share credentials using a secure passe and distribute it only to the autorisés. Note the ladresse they will use to access the assets. This cest an important control point.
étape 2: Define permissions by case and keep the total scope minimal. Use per-case basis to limit exposure; voir the permissions summary and adjust as needed. If you offer multiple forfaits, map each to the required tasks so the partner sees only what they need. Provide a brief lecture on security best practices to the partner and document decisions for the listes of changes; you can also cliquez to save the configuration.
Final checks: voir activity logs, revoke access when the project ends, and ensure the setup remains complète. If ongoing collaboration is required, create a limited forfaits with clear boundaries and review monthly. Keep the process transparent for vous and the partner, and confirm the final status in meta by clicking to verify (cliquez).
Determine the required role and assets to share with the third party
Start with the smallest scope: grant the third party an editor role on the principal compte voor de page they will manage, and keep all other assets locked down. Use a temps-bound invitation to control access duration.
Define assets by listing types of assets, including the page, compte and related publicité objects, catalogs, and pixels. Identify the relevant segments en groupes that the third party will touch. Limit UI interruptions like pop-ups and document the источник of data used in the collaboration.
Assign roles by task using manager en éditeur designations; avoid giving admin on the compte. For secondaire work, scope the secondaire layer and reserve the principal assets for primary tasks. Use the droite déroulant menus to switch roles and scope quickly while keeping tracking.
When onboarding, soumettre an invitation only after the scope is defined. Organize access by groupes to simplify rotation and audits; create separate invites for each asset group (page, publicités, types, etc.) to avoid cross-access.
Security checks: ensure all grants are autorisé and auditable; the laide from the security team helps verify compliance. Prevent extraction by the third party: prohibit copier of sensitive data and cap access to the designated источник. Avoid sharing credentials and apply sécurité best practices, mais sans exposing critical data.
Track decisions and plan for futures: document decisions, set a cadence for reviews, and use the droite déroulant controls to adjust rights. Record the temps windows, источник, and outcomes to support ongoing collaborations with the third party.
Invite the third party via Business Settings > People or Partners
Open Meta Business Suite and in the meta business settings click Invite under People or Partners to begin. Enter the third party’s email, then choose an access role: use éditeur for full editing or lautorisation limitée for tighter contrôle. Sélectionner the assets to share and consultez the permissions map to determine what actions are allowed, aligning with votre daccès and the nécessaire safeguards. Finally invitez the partner to accept the invitation.
Steps to invite
1) Navigate to Business Settings and select People or Partners.
2) Enter the partner’s email and choose the access role (éditeur for full editing, ou lautorisation limitée for restricted actions).
3) Sélectionner the assets to share (Pages, Ad Accounts, Catalogs) and ajustez the daccès scope according to nécessaires, coordinating avec propriétaires if needed.
4) Send the invitation and monitor the status in the suivi panel until the partner accepts.
Assets and permissions
| Asset | Access option | What it allows |
|---|---|---|
| Pages | Éditeur or Limited access | Publish posts, respond to messages, moderate comments (permissions depend on role) |
| Ad Accounts | Manage ads or View only | Create campaigns, adjust budgets, access reports |
| Catalogs | Manage products | Update product details, add or remove listings |
Use the maximum fonctionnalités you need, and apply the payantes components only if required. If changes are needed, soit convert the access level by updating the role, ensuring vous retain contrôle while expanding capabilities when justified. Keep the suivi active to track 활동 and ensure that you stay compliant with les propriétaires and policy requirements.
Assign specific assets (Pages, Ad Accounts, Pixels, Catalogs) to the invited user
Configure per-asset permissions and optional expiration if available
Best practice: grant per-asset access starting with the asset on the left (gauche) in the l’écran. Choose the lequel asset to apply and assign a minimal rôle to each contact (contacts). Use niveaux to define scope and, when supported, set a paramètre d’expiration so access expires automatically. This approach keeps audits clean across projets and ensures each lidentifiant is tied to the right compte. Note the string reçoit may appear in logs as a trace of requests, and remember to document chaque action for each propriétaire.
Note: include the token lidentifiant (without the apostrophe) for cross-reference; add it to your records so audits and communications stay accurate.
- Identify assets to share: pages, ad accounts, catalogs, and pixels. Record the total (total) and note each l’identifiant for future reviews; this helps propriétaires know who has access to which asset.
- Open the asset permissions panel: in the left navigation (gauche), click the asset name (lequel) to reveal the permissions options on the l’écran and verify current access levels.
- Add collaborators: use the option ajoutez to bring in new contacts. Enter each l’identifiant and assign a role (rôle). For chacun des nouveaux partenaires, keep the assigned niveaux tight to avoid excess access.
- Choose per-asset permissions: select an appropriate niveau such as Viewer or Editor rather than Admin; apply the setting only to the selected asset to prevent cross-asset leakage.
- Set optional expiration: if the feature is available, configure the expiration date (passe) or duration for that asset. If expiration isn’t available, place a reminder to envoyer and revoke when the project ends; this lets you rejeter access cleanly, for example after the dune of the projet.
- Validate and document: review all permissions for each asset touched, and confirm that the total access aligns with the project scope. Keep notes for les propriétaires and update the compte entries as needed.
Confirm delivery of the invitation and verify access from the third party
Verify delivery immediately by checking both the email and the invitation status in Meta Business Suite. In Settings, go to Partenaires and review the total invitations, focusing on the quinvité entry in the existantes listes. Cette vérification spécifique couvre les intégrations et la validité de la livraison; si le statut est pending, cliquez “Resend invitation” pour le réémettre et assurer qu’il arrive automatiquement dans la boîte de réception du destinataire.
Steps to confirm and verify access
Ask the third party to check their email and the Messages center for the invitation. They should cliquez the link and complete the lecture to accept access. If the invitation is not visible, verify the email in contacts and reissue the quinvité à la bonne adresse.
After acceptance, verify that the access is correctly granted: the partenaire entry must show autorisé and the statut should reflect the new permissions. Review the champs that control what they can do (view, edit) and ensure they are aligned with the projets they should manage. Cela vous aide à faire un suivi clair et à documenter les décisions pour le case et les listes existantes. If you need adjustments, perform them as administrateur and, where applicable, update the souscrit settings to reflect the new access.
Monitor ongoing access and adjust or revoke permissions as needed
Start with a fast audit: open the Menu, go to Settings > People, and export the current access report. Note chacun des invités, their role, and the zones of destination assets they can reach. Verify appartenance and confirm that each invitation matches the project scope. If you spot payantes partners with broader access than nécessaire, mark them for removal and prepare a revoke action. Keep a concise note for traceability.
To adjust, mettre en place the changes: in the paramètre controls, assign the minimum nécessaires rights to each invité. Désactiver d’invité for those no longer involved; if a member must stay, set a secondaire role or assign them comme administrateur for ongoing oversight. Use the droite menu and the menu to refine the zones and destination assets, limiting access to what’s strictly necessary. partagez the updated configuration with chacun; this lets you faire adjustments when conditions change.
Ongoing monitoring requires a cadence: set expiry dates and revoke immediately if no longer needed. Télécharger a fresh log weekly or monthly; recevra updates and annotate the changes with a note. If someone recevra a new access request, route it through the standard approval workflow before applying changes.
Cadence and governance: enforce a regular review cycle for non-critical access and contractor permissions. For zones with publicitaires assets, ensure only approved agencies have access and that their droits are limited to the destination assets they manage. These changes sont aligned with policy; keep the administrateur role informed, and document decisions in a shared note to maintain clear appartenance and accountability.
Reacties