My Access, reached from your Profile menu, lists your data product access requests grouped into a tree: first by the data product’s data domain, then by data product underneath it. Domains are listed alphabetically, with a Without a domain bucket last, for products that carry no domain.
Expanding a product separates what it shows into three parts:
- Active access: the requests already granted and set up, with the access tier, port count, and expiry summarized on the row. The summary counts every live agreement of the product, and shows the access tier only when it’s the same for all of them.
- Requests: the ones still moving toward a decision, plus requests with the status Handed to administrator (with a date). These are approved requests sent by email for a platform administrator to set up. They count as in progress in the group header, not as active.
- History: closed requests, rejected, cancelled, expired, or ones whose provisioning failed. Collapsed by default, so a product’s history does not crowd out what is still active or pending.
One row per output port
Within each part, a product shows one row for every output port you requested access to, not one row for the whole product. If you selected two ports in one request, you see two rows, each with the port’s name and its own status, request number, date, agreement, and access expiry, because each port is approved and granted separately.
| Case | Behavior |
|---|---|
| Renewals and further requests under the same port | A renewal, and any follow-on request from it, appear under that port’s row instead of as separate entries. Expand the row to see all of its requests (number, kind, status, and date, newest first), and select one to open its detail, where you can read the outcome and reason of a rejected renewal while the original access stays active. |
| Access expiry | The row shows the end date of the port’s active agreement, even while a renewal is still waiting for a decision. The pending renewal is visible from its own status in the list. |
| Scope unavailable | A request whose port couldn’t be identified is listed under its product as a separate row labeled Scope unavailable, with its own status. It isn’t counted in the product’s port total. |
The counts in the group headers and the “shown of total” counter on the page count these port rows. The search, status, and date filters apply to the rows, so filtering never splits a port’s renewals away from it.
Approval timeline
Expanding a request shows its Approval section: the decision chain your organization’s policy applied to it, with one step per role (Owner, Data protection officer, or Security officer, depending on how sensitive the request is). For a request on a single port, the Owner step is that port’s Data Owner. See Working with ports.
| Step state | What it shows |
|---|---|
| Decided | Who approved it, by name where Dawiso could resolve one, otherwise by the address the access-management service recorded, along with when. |
| Currently being decided | Marked as waiting for a decision. |
| Not yet reached | Marked as not yet reached. |
| Skipped | Marked Skipped, along with the reason it was skipped rather than being left out. |
When the administrator confirms the setup, the request moves to Active access. This happens within about a minute, because the list refreshes every minute, or when you refresh the page.
Request detail for access set up by an administrator
Opening a request that was handed to an administrator shows an information banner:
- Approved request: “Approved and sent to the platform administrators. They set up your access and let you know when it is ready.”
- Auto-approved request: “No approval needed. Sent to the platform administrators, who set up your access and let you know when it is ready.”
The status badge shows the date. The access tier and row-scope fields aren’t shown, and in the port table the channel appears as “Email · date” and the platform as “External source”.
A rejected request shows a warning banner with Reason for rejection, the reason, who rejected it, and the date.
Renew or request more access
A request’s detail panel offers two shortcuts back into the request flow, so you do not have to find the product in the Data Market again:
- Renew access: shown once the request is active, and also on a request handed to an administrator, for continuing access you already hold.
- Request more access: shown on every request, for asking for more than that request covers.
Both re-add the product to your cart, carrying over the duration, the output port, and the row scope (limited or not) of the row you clicked from, and take you straight to the cart to submit a new request. See Requesting access to a data product for how the request flow works.
Cancel a request
A request’s detail panel offers a Cancel request action for as long as the request is still moving toward a decision. Once your organization has approved it, the action no longer appears.
Selecting it opens a confirmation dialog that names the request and the data product it is for, and warns that “Cancelling cannot be undone. To get this access you would have to submit a new request.” Confirming updates the request’s status to cancelled right away. If the access-management service refuses the cancellation, for example because the request had already moved on to a later stage, the status reverts to reflect what actually happened.
Troubleshooting
Connection isn’t configured
If your organization’s access-management service was never connected, My Access shows a warning banner: “The connection to the access service is not configured. Contact your administrator.” Unlike the banner shown when the service is temporarily unreachable, this banner has no retry action, because there’s nothing to retry until an administrator sets up the connection.
List looks incomplete or shows an error
- If you have an unusually large number of access requests, My Access may not be able to retrieve all of them in one pass. When that happens, it tells you the list is incomplete rather than silently cutting it off.
- If the access-management service cannot be reached, My Access shows an error instead of an empty list. An empty My Access always means you genuinely have no access requests, never that something has gone wrong.
My Access is unavailable
My Access only works when Dawiso itself tracks your organization’s access requests. If your organization instead routes requests through Jira Service Management or ServiceNow, My Access doesn’t appear in your Profile menu, and you track your requests there instead. Check with your Dawiso administrator if you aren’t sure which applies to your organization.