Tenants
I am now seeing my use case for tenants and wondering about functions that will support it and whether I am on the right track. I can see it would be great if fully implemented.
I have an application with Employers and Jobseekers (so two different user groups/apps). They negotiate employment.
So I have created a separation based on Organisations: Business and Jobseeker
As they negotiate employment, I trigger the jobseeker workflow and add the business as the tenant.
Things I would expect in the web UI:
* filter activity feed on tenant
* test workflow with tenant field
In the API:
* 'tenant' field in the event looks to be polymorphic between string and {identifier: string}—just plain confusing and have to go to source code to reconcile UI curl versus API documentation
* tenant errors when no tenant found—given other 'PUT' like behaviours adding the tenant would be consistent and great
* corresponding to UI, I was expecting /notifications to have the tenant dimension—why not, just wondering?
I have an application with Employers and Jobseekers (so two different user groups/apps). They negotiate employment.
So I have created a separation based on Organisations: Business and Jobseeker
As they negotiate employment, I trigger the jobseeker workflow and add the business as the tenant.
Things I would expect in the web UI:
* filter activity feed on tenant
* test workflow with tenant field
In the API:
* 'tenant' field in the event looks to be polymorphic between string and {identifier: string}—just plain confusing and have to go to source code to reconcile UI curl versus API documentation
* tenant errors when no tenant found—given other 'PUT' like behaviours adding the tenant would be consistent and great
* corresponding to UI, I was expecting /notifications to have the tenant dimension—why not, just wondering?
