Your workflow is unique 👨💻 - tell us how you use Dropbox here.
Forum Discussion
Solved
Difference between sf_nonteam_add_members , sf_nonteam_join & sf_nonteam_claim_membership
Hi There,
What is the difference between sf_nonteam_add_members , sf_nonteam_join & sf_nonteam_claim_membership.
Thanks,
Manish
Doing a little more digging into this, if you refer to our v1 docs for the get_events endpoint there is an entry under the notes section that states:
- The events
sf_team_mountandsf_nonteam_mountwill eventually replacesf_team_joinandsf_nonteam_join.
I'm thinking this is why you're not seeing the sf_nonteam_join events when a non-team member joins/mounts shared content.
I do want to reiterate that these event types are all v1 and that migration to v2 is highly recommended. The following content can help with that process:
https://www.dropbox.com/developers/reference/events-migration-guideFor a brief description of what actions cause what events see the event types section of the v1 documentation:
https://www.dropbox.com/developers-v1/business/docs#log-get-eventsThe events migration guide referenced above shows the mapping of v1 categories to v2 categories.
I hope this gives you the information you are looking for. Thanks!
-Chuck
- The events
6 Replies
- chirstius
Dropbox Staff
Hello Info V.1,
The events you reference are v1 event types, so first I'd like to suggest you look at migrating to the v2 event log endpoints:
https://www.dropbox.com/developers/reference/events-migration-guideThe event types you mention refer to different actions performed by non-team member actors specifically as related to a shared folder, so for example:
sf_nonteam_join refers to a non-team member joining a shared folder.
sf_nonteam_add_members refers to a non-team member adding members to a shared folder and so on.
Under v2 these events have all been collapsed under shared_content_xxxx event types (complete descriptions in the migration guide referenced above) and the determination of whether the action was performed by a team member or not can be achieved by examining the actor and context properties of the event entry.
Hope that helps,
-Chuck
Thanks for the quick response . We have planned for migrating to V2.
I am seeing different behavior:
As a team admin I added a non-team user (exist in Dropbox) and I get "sf_nonteam_add_members".
As a team admin I added a non-team user (does not exist in Dropbox) and I get "sf_nonteam_invite". And when the new user created Dropbox account I get "sf_nonteam_claim_membership".
I am not getting "sf_nonteam_join" in both of the above cases.
Thanks,
Manish
- chirstius
Sorry about that, I think I inverted the relationships.
Have you had a non-team member (but Dropbox account) mount the shared folder?
Yes, when non-team user mounted the folder then I get "sf_nonteam_mount" event.
- chirstius
Doing a little more digging into this, if you refer to our v1 docs for the get_events endpoint there is an entry under the notes section that states:
- The events
sf_team_mountandsf_nonteam_mountwill eventually replacesf_team_joinandsf_nonteam_join.
I'm thinking this is why you're not seeing the sf_nonteam_join events when a non-team member joins/mounts shared content.
I do want to reiterate that these event types are all v1 and that migration to v2 is highly recommended. The following content can help with that process:
https://www.dropbox.com/developers/reference/events-migration-guideFor a brief description of what actions cause what events see the event types section of the v1 documentation:
https://www.dropbox.com/developers-v1/business/docs#log-get-eventsThe events migration guide referenced above shows the mapping of v1 categories to v2 categories.
I hope this gives you the information you are looking for. Thanks!
-Chuck
- The events
Thanks Chuck !!
About Dropbox API Support and Feedback
Get help with the Dropbox API from fellow developers and experts.
