-
Notifications
You must be signed in to change notification settings - Fork 79
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
Question about how to have multiple users on an account #2993
Comments
You can use
You need to create an Editor first before you can assign that editor to a Book (or other content types like Essays and Poems). When you create a new Book, you specify the editorID, which references the existing Editor's id. This establishes the relationship between the Book and the Editor in your database. So,
The answer is yes. |
The
In this case, the |
Thanks for letting me know. @bobbyu99 I tried to explain this over some of the amplify live chats but they couldn't understand the scope of the problem. The current application I am building - it seems like this would be an expensive operation. Especially because some of the data points are just site visits and other similar small data points that add up very quickly. Is there a different architecture approach to solve this other than just making the functions manually? I could create a separate instance for each company that bought the solution right? like _____.app.com and then have them call in whenever i needed to change someone's permission to "editor" or some other "admin" equivalent without loosing to much time. |
Have you tried Dynamic group authorization? For example:
Since access is granted based on group membership, adding a new editor to the group |
No i haven't tried this yet. I will have to do some backfilling it seems like, but this could work. Is there documentation on how to enable a user to create and add people to those dynamic groups, like from a lambda function invoked by a custom mutation? |
I don't think there is a documentation for this. But you may find the following uesful: |
Here is the documentation: https://docs.amplify.aws/gen1/react/tools/cli/usage/lambda-triggers/#auth-templates |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Amplify CLI Version
12.13.0
Question
I am confused about how to make an organization type of schema, and the right way to update roles and permissions on items. I'm on gen 1.
Lets say I create a website that is for publishers. They can create, books, essays, poems, and etc... There are owners, editors, and readers.
... something similar for the other ones.
I have a different table for my editors, and a mechanism for getting their userID.
Lets say I have created a 10 books, 22 essays, and 3 poems. Do i have to manually update all of the previous records with the user ID Whenever I create a new editor?
I know there are also groups, that can be updated in cognito like the "admin group" but that is across all of the books, from all the owners. If I added people to a group called editors, they would be able to edit everybody's book which i do not want.
I created an application called schedulevolunteers.com - to solve it in that one I had to create custom read operation for each one, that checked the nonProfit Entity table, to see if they had the permissions, or if they had been updated, and then update each record before they saw whatever it was they wanted to see, so they could make mutations. Is there an easier way to do this?
this i that schema so you can see a non trivial example. this was suppose to be for non profits - it helped one museum for a second but nobody use it anymore.
GraphQL Schema
The text was updated successfully, but these errors were encountered: