Creating Team Memberships in Appwrite for a Multivendor Application
- 0
- Teams
- Databases
- Web
- Self Hosted

I'm developing a multivendor application that allows users to create groups and assign different roles to members. I'm using AppWrite's Teams API to manage the groups, but I'm having trouble working with memberships. The documentation doesn't seem to match the actual behaviour of the API. Can you please provide guidance on how to create team memberships using the AppWrite server SDK? I have included screenshots of my function logic and a snippet of the error I'm getting when I try to invoke the function.

Sorry guys. While digging up I realised that the event payload is passed as a string not an object. Therefore I had to first parse it into a JSON object then use the values in the json string. The team API works fine. Finally got the membership functional.

It worked but in the documentation it is saying that the email option is not optional when creating a team if argument is passed as an empty string. There is need to fix this in the documentation.

I'll raise an issue

How can I raise it anyway

Creating Team Memberships in Appwrite for a Multivendor Application

You can create an issue on GitHub: https://github.com/appwrite/appwrite/issues
However, before you do that, it looks like you're using the SDK and referring to the docs for Appwrite version 1.3.x, but your Appwrite is version 1.2.1

Please upgrade (https://appwrite.io/docs/upgrade) and try again

Thanks.
Recommended threads
- appwrite cli alpine os
the appwrite cli does not work on alpine os if you install it using the recommended bash script. Maybe there is the possibility to compile it for alpine using t...
- Invalid document structure: Unknown attr...
I have an attribute, who I deleted but it still gives error saying that Invalid document structure: Unknown attribute: "financialAidAvailable". Because of which...
- Migration to new region: not so good.
We attempted to do a migration to NYC... and things didn't go well. We followed the steps (exactly) as shown in the video, updated our app with the new endpoint...
