> ## Documentation Index
> Fetch the complete documentation index at: https://help.autoady.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Review accounts in Portfolio

> Use existing Portfolio access to triage accounts without blending currencies or hiding failed actions.

If **Portfolio** is already available in your workspace, open it to decide which Meta account needs attention first. If it is absent, use the sidebar account selector and [review accounts individually](/meta-ads/performance). An Agency plan name alone does not guarantee Portfolio access.

## Review the account list

1. Open **Portfolio** and choose a reporting range.
2. Review the totals and account rows. Money is shown in native currencies; mixed currencies must remain separate. A missing CPL or ROAS is not zero.
3. Use the review filters or **Search accounts**, then expand a row for its account details.
4. Open the account's dashboard or Intelligence review to investigate the underlying campaigns.

Unavailable accounts are excluded from the totals. Expand the unavailable-account notice and use **Review Meta connections** to check access. If an account is missing, inspect connections and the account selection rather than assuming it had no spend.

## Portfolio operations

Where your role has access, expand **Portfolio operations** for **Groups**, **Pacing**, **Inbox**, and **Bulk actions**. Check each group's membership, native currencies, and reporting dates before comparing totals or pacing. Pacing is an estimate against the available budget envelope, not a spending cap.

For a bulk action, inspect the exact accounts and entities in the confirmation before proceeding. Verify each returned outcome and partial failure; a successful item does not establish that the whole batch completed. Recheck the affected account in Meta or its AutoAdy table before retrying a failed item.

If Portfolio or its operations are unavailable, use the sidebar account selector and [review accounts individually](/meta-ads/performance). [Client workspaces](/workspace/clients) organize access and associations separately.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.