Filter activity by action

Filter activity by action with a controlled test, clear verification, limits, and recovery steps.

Last reviewed

Filter activity by action is easier to verify when you use one controlled item and check the account, workspace, and destination at every step. This guide follows the current Dosya workflow and calls out the result you should see.

Before you start

  • Open Activity log in the current released client.
  • Confirm the active account and workspace, then identify Action filter after optionally choosing a category.
  • Use a small non-confidential test item and record its current state before changing it.
  • Keep passwords, API keys, recovery keys, private links, and personal client data out of screenshots and support messages.

Steps: filter activity by action

  1. Open Activity log and confirm the active account and workspace.
  2. Locate Action filter after optionally choosing a category and verify its name or identifying details.
  3. Select the precise action type and reset to page one.
  4. Read the displayed warning, permission, progress, or confirmation state before leaving the screen.
  5. Confirm that the list narrows to matching action rows.
  6. Refresh or reopen the relevant view once to verify the result persisted.
Dosya workspace Activity log with category, member, and action filters.
You need the workspace activity permission; use the time and resource name to distinguish similar events. Open full-size screenshot.

Expected result

The controlled workflow completes and the list narrows to matching action rows. The result remains visible after a refresh, reconnect, or return to the relevant screen.

Limits and important details

  • Available controls depend on the current client version, account plan, workspace role, and policy.
  • Processing, indexing, background transfer, or third-party authorization can delay a visible result.
  • For destructive, access-changing, or automation actions, validate with disposable data before applying the workflow to important files.

Troubleshooting

The expected control is missing. Return to Activity log, confirm the active workspace, and check that your role and client version support the action.

The operation is rejected or stalls. Read the exact message and check permissions, locks, storage, network state, source availability, and any third-party authorization before retrying.

The result is still unclear. Repeat with one small test item, then contact support with the time, client version, workspace, and a nonsecret error or request identifier.

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.