-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
component: dashboardfeature: billingmeta: never-staleThis issue can never become staleThis issue can never become staleteam: webappIssue belongs to the WebApp teamIssue belongs to the WebApp teamtype: improvementImproves an existing feature or existing codeImproves an existing feature or existing code
Description
Problem to solve
Following up from #11554 (Cc @laushinka @easyCZ @jldec), the usage tab is currently visible to all team members regardless their role. However, access to non-owners is restricted, and the usage tab currently included a no access placeholder.
Issues with the current approach:
- The application feels like something broke without providing sufficient feedback to users.
- No call-to-action (CTA) on how to resolve the restricted access issue.
- Promoting a feature by making the usage tab visible and making the feature inaccessible not because of the user's subscription, but because of their team role can be confusing as it will probably be impossible for a user to change their role as this contradicts the initial goal of having roles in teams. This issue will become more obvious for larger teams which usually require specific role access so that they can control data access, and more.
Usage (Owner) | Usage (Member) |
---|---|
![]() |
![]() |
Metadata
Metadata
Assignees
Labels
component: dashboardfeature: billingmeta: never-staleThis issue can never become staleThis issue can never become staleteam: webappIssue belongs to the WebApp teamIssue belongs to the WebApp teamtype: improvementImproves an existing feature or existing codeImproves an existing feature or existing code