Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/acl b2b suite management permission #182

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Josmar-jr
Copy link
Contributor

What problem is this solving?

This change addresses the issue where any user can make changes to the organization management interface, without any control over who can view or edit. The goal is to implement a minimum level of access control for viewing and editing organizations, using existing resources in the License Manager called Buyer Organization View and Buyer Organization Edit.

How to test it?

  • Test with different user roles:
  • Admin users should be able to access the application and perform all actions as before.
  • Users with Buyer Organization Edit resource should have full access to view and edit organizations.
  • Users with only Buyer Organization View resource should be able to view organizations but not make any edits. Ensure that buttons like "New", "Save", and "Add Field" are disabled.
  • Regular users without these resources should see a notification indicating lack of access to view or edit organizations.

[Workspace](Link goes here!)

Screenshots or example usage:

Screenshot 2024-11-07 at 10 14 11 Screenshot 2024-11-07 at 10 13 10

Describe alternatives you've considered, if any.

Related to / Depends on

How does this PR make you feel? [🔗](https://media.giphy.com/media/9PKVHmnLEW3nkHV6i5/giphy.gif?cid=ecf05e47jpnlm9g3up6qj12skm72uqlq4a2i58xym1lmqdgn&ep=v1_gifs_related&rid=giphy.gif&ct=g)

![](put .gif link here - can be found under "advanced" on giphy)

Copy link

vtex-io-ci-cd bot commented Nov 7, 2024

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

  • Patch (backwards-compatible bug fixes)

  • Minor (backwards-compatible functionality)

  • Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

  • No thanks, I would rather do it manually 😞

@vtex-io-docs-bot
Copy link

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

  • There's nothing new to document 🤔
  • I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

  • I just updated 🎉🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant