Find shared work¶
Use Shared work to locate packages exchanged with connected workspaces. Check the direction, other workspace, subject and current status before opening an item.
Availability: These steps follow the current Final Screens browse designs. The inspected frontend is still a preview: its packages, totals and states are examples, and its search, direction links, paging and row actions are not connected to live work. The backend supports the list behavior described below. Ask your workspace administrator which connected functions are available in your environment.
Before you start¶
Sign in to the correct workspace. Have a work title, a distinctive part of its summary or a primary-file name available if possible. If someone else sent you a reference, confirm that it belongs to this workspace and whether the work was received or sent.
Received packages are limited to work in which your account participates. The Sent view reads outgoing work for the workspace, not just your own submissions. Do not use another person's account to find an item you cannot access.
Find a package¶
- Open Shared Work in the WorkOS navigation.
- Choose All, Received or Sent in the direction control. All combines the received and sent work that the current read allows.
- Enter a distinctive title, summary phrase or file name in the search field. Choose a status when you want to narrow the result, then select Search.
- Read the matching row's work title, summary, direction, other workspace, status and requested interaction. Compare the file name and other available file details when similar titles could identify different packages.
- Select Open on the intended row. The design takes you to that package's detail; the inspected preview does not yet prove navigation to a selected live package.
- Use Previous and Next when the result spans additional pages. Recheck the direction and filters if a package is not on the current page.
The wider design includes a guidance panel alongside the table. The inspected 1440-pixel design omits that panel but retains the direction, search, status, rows and paging controls. Share work starts the sending journey; it is not needed to search existing work.
Expected result: The connected list returns matching work within your access, and you open the intended package. Opening a row is a read, not an acceptance, rejection or filing action.
Search within the supported fields¶
Search checks the stored work title, summary, primary-file name and the system's capability key. The capability key identifies the kind of work offered by a receiving workspace; it can differ from the friendly capability name displayed in the list. Searching that displayed name is therefore not guaranteed to find the package. Try the title or file name instead.
Search does not check the readable workspace name, a person's name, an owner label or the document's contents. The older frontend preview has broader search wording; that wording does not establish supported search. Ordinary text is the most predictable choice because special pattern characters can broaden matches.
Direction and status are applied together with search. A search can return no results because one of those filters excludes the package even when the text is correct. Broaden one filter at a time so you can tell what changed.
Interpret rows and totals¶
| Information | How to use it |
|---|---|
| Work title and summary | Identify the subject and distinguish similarly named packages. A summary may be absent. |
| Received from or Sent to | Establish the direction and other workspace. If the name is missing, confirm context before acting. |
| Status | Read the recorded exchange state. Do not substitute a preview label, requested action or file condition for that state. |
| Interaction and capability | Understand the kind of exchange and what was requested. They do not grant permission to perform every action. |
| Primary-file details | Identify the file when metadata is available. Size, version and change notes may be absent; absence is not a zero size or a first version. |
| Result count and page | Understand the current matching scope, not an unrestricted enterprise total or a count of overdue work. |
Results are ordered by the latest exchange-state change first. They are not ordered by a deadline or by whether you have read the file. Counts and pages are loaded separately, and work can change while you browse. If a page becomes empty or changes unexpectedly, refresh the list and start again from the first page before concluding that work has disappeared.
The current browse response has no separate Archived direction, due-date filter, saved-filter service, unread measure or direct-download action. Those controls or values in an older sample preview should not be relied on as live capabilities.
Recover from missing or incomplete results¶
| What you see | What to do next |
|---|---|
| No matching packages | Check the workspace and direction, remove unnecessary search text, broaden the status and try a known title or file name. Check further pages when present. |
| A colleague can see received work that you cannot | Ask an authorized owner or administrator to check your recorded participation. A filter change cannot grant access. |
| A workspace or capability name is missing or looks unfamiliar | Retry the read. If ambiguity remains, ask support to verify the package's context before making a decision. |
| No primary-file details, or only some details | Read the package context. Do not interpret missing metadata as proof of deletion, permission to download, or a usable document session. |
| The list fails to load | Check connectivity and retry the read. An error is different from a successful empty result; do not resend work solely because the list failed. |
| A row opens an unavailable or restricted detail | Confirm the selected workspace and package with an authorized person. Access or recorded state may have changed since the list was read. |
| The sample preview does not respond | It may still be a design preview. Confirm availability with your administrator rather than treating the sample as an operational record. |
For help, record the visible message, approximate time, workspace, package title and filters. Avoid attaching confidential files to an unrestricted support conversation. Do not create another package simply to compensate for an uncertain read.
Continue with Read a shared-work package for the detail sections, routing, people, status and history. Return to Shared work between workspaces for the business meaning and related capabilities. Use Send work and Accept, reroute or reject for their intended steps and recovery limits; browsing alone does not establish authority for those actions.