Administrator can create a new Company (Update/List/search/etc)
When a user requires to become a service provider he may specify the Company uniqueId (6-8 chars)
Administrator can approve the ServiceProvider and define its role in the Company (each Company must have at least 1 manager)
Company Manager is authorized to invite (via email) any user to login and join its company as member: the link sent via email does NOT check the user login with the same email address.
Each User is currently connected with 1 and only Company (defined during login process)
When a TX is registered in DB, it should always contain the author username and the company he is working for. All queries to retrieve data about ServiceRequests, Offers, etc are done using the Company UID (today we check the userId)
This change is needed so that all colleagues of the same Company see the same data and if a User change Company he is not authorized to see Company data anymore.
Administrator can create a new Company (Update/List/search/etc)
When a user requires to become a service provider he may specify the Company uniqueId (6-8 chars)
Administrator can approve the ServiceProvider and define its role in the Company (each Company must have at least 1 manager)
Company Manager is authorized to invite (via email) any user to login and join its company as member: the link sent via email does NOT check the user login with the same email address.
Each User is currently connected with 1 and only Company (defined during login process)
When a TX is registered in DB, it should always contain the author username and the company he is working for. All queries to retrieve data about ServiceRequests, Offers, etc are done using the Company UID (today we check the userId)
This change is needed so that all colleagues of the same Company see the same data and if a User change Company he is not authorized to see Company data anymore.