I have been researching how my company's application could integrate with Box and it makes a lot of sense until getting to the metadata templates. By the sounds of it, the metadata templates are for enterprises that use box to do their business and create tools to add in custom metadata to their files/folders...
But I am curious if a third party app (essentially my company's app) can create metadata templates and apply them to files the users use within our app? I read that certain box accounts need to pay for the metadata addon and it sounds like it is more of a... internal use only use case.
For some more context our app wants to be able to expose metadata that our app uses (and that the user creates by using our app), which could be valuable to the users of our app AND allow enterprises/users to be able to store their files, metadata included, in Box. This would allow them to have greater control over their data/files and our app can still work with their files without having to store the metadata/file contents. Essentially separates our app from the data but can still manipulate/edit the data/files as needed.
I noticed in the API documentation the metadata template needs a scope which applications can only create enterprise level scopes; So with the context explained up above, would we have to create a template for each enterprise, even though they are the same?
If anyone could help explain or give me some insight I would greatly appreciate it! I can't seem to discern the answer. I am curious if it is just a misunderstanding, or there is more nuance to the situation.
Please sign in to leave a comment.