Replies: 12 comments 1 reply
-
A user 🔒 says: It would be nice to have different roles with different permissions ex. the Scrum Master would have administrative capabilities but there could also be a facilitator role with fewer permissions on a team or org |
Beta Was this translation helpful? Give feedback.
-
A user 🔒 said:
|
Beta Was this translation helpful? Give feedback.
-
A customer 🔒 asks:
|
Beta Was this translation helpful? Give feedback.
-
A customer 🔒 writes:
|
Beta Was this translation helpful? Give feedback.
-
A customer 🔒 writes in response to our existing enterprise report:
I think these suggestions would be great to think about as we design an admin board/view |
Beta Was this translation helpful? Give feedback.
-
A customer 🔒 writes:
|
Beta Was this translation helpful? Give feedback.
-
A user 🔒 writes:
|
Beta Was this translation helpful? Give feedback.
-
Our pals at this company 🔒 would like a way to map Identity Entitlements (i.e. "administrator") to a permissions level in Parabol (i.e. "Billing Leader") |
Beta Was this translation helpful? Give feedback.
-
A few notes here: In Oct 2021 we had a design sprint to address big ideas and opportunities around admin. The artifacts are here in Figma and I’ve drafted some notes on the process in Notion. We focused on a goal of providing customers the information they need in order to move forward with a purchase. Today this is a manual process and one of the first leaky points today. How could we build a first set of interfaces to provide them with more of this automatically? Later we would realize what controls we need for ongoing administration of the account. We focused on 2 questions: 1) how much domain-wide information is too much to share? and 2) what kind of basic administration needs do they expect around members (licensed seats, active or inactive) and team insights? The list of concerns in the top comment is rather long, indeed warranting broader exploration. In our prototype we did imagine a basic, high-level IA where certain concerns would be sub-views of top-level sections: Insights, Members & Teams, Plan & Billing, Advanced Settings, and Support. We were inspired by services like Google Fi that allow high-level navigation to dive down into details. We should consider expanding these sections 1 at a time with a second level nav for a handful of specific areas each, like e.g. SAML/SSO under Advanced Settings. What I want to do here is convert this issue (originally #4407) into a 👂 Feedback discussion item, since it has a lot of verbatim from customers. And then write some smaller issues representing different areas of concern mentioned in the initial comment and takeaways from the design sprint. Many of these should be discussions or smaller, specific design scopes. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Here’s feedback from another user who wants an admin role that can see and invite to all teams on the org (implying they don’t have to be a team member to see the teams etc.) |
Beta Was this translation helpful? Give feedback.
-
Issue - Enhancement
Originally #4407
As the IT administrator of Parabol—either cloud-hosted or privately hosted—I want to:
Questions to consider during design
Acceptance Criteria (optional)
A series of lo-fi designs
Feedback collected from the internal team
Estimated effort: 15 points (see CONTRIBUTING.md)
See also:
Beta Was this translation helpful? Give feedback.
All reactions