This object is in archive!
How To Support Separate Communities ...One Domain
We need to support 3 different communities ....
Property Owners
Contractors & their Users
Insurance Companies & their Users
We are claimexpress.com and we sell access to a private application to each of these types of User Entities...
Contractors user only see the responses from other contractors
Property owner's only see the responses from other property owners
Insurance Company users only see the responses fro other insurance company users...
Customer Service Chat's with all of them and moderates the responses
We will provide the link to support from within our application..therefore the access control and Users would need to be integrated with our system....
Any ideas...
Donald,
1) You can install one license on one URL - more about this is discussed here
2) To make what you are required within one community is impossible with standard features and will require customization. One of the way is to use categories for each of your products and delegate permissions to specific user groups in the system that are set up at Administration > Roles to specific category to have access and see it along with Private Objects module
3) To integrate authentication into your system it will require Single Sign On that we are working on currently.
If you don't want to take time on customization, you'll have to purchase 3 licenses for each URL, but we recommend you using one license with Categories module to distribute responses between them, but they will be visible to all members
Donald,
1) You can install one license on one URL - more about this is discussed here
2) To make what you are required within one community is impossible with standard features and will require customization. One of the way is to use categories for each of your products and delegate permissions to specific user groups in the system that are set up at Administration > Roles to specific category to have access and see it along with Private Objects module
3) To integrate authentication into your system it will require Single Sign On that we are working on currently.
If you don't want to take time on customization, you'll have to purchase 3 licenses for each URL, but we recommend you using one license with Categories module to distribute responses between them, but they will be visible to all members
Donald,
1) You can install one license on one URL - more about this is discussed here
2) To make what you are required within one community is impossible with standard features and will require customization. One of the way is to use categories for each of your products and delegate permissions to specific user groups in the system that are set up at Administration > Roles to specific category to have access and see it along with Private Objects module
3) To integrate authentication into your system it will require Single Sign On that we are working on currently.
If you don't want to take time on customization, you'll have to purchase 3 licenses for each URL, but we recommend you using one license with Categories module to distribute responses between them, but they will be visible to all members
Donald,
1) You can install one license on one URL - more about this is discussed here
2) To make what you are required within one community is impossible with standard features and will require customization. One of the way is to use categories for each of your products and delegate permissions to specific user groups in the system that are set up at Administration > Roles to specific category to have access and see it along with Private Objects module
3) To integrate authentication into your system it will require Single Sign On that we are working on currently.
If you don't want to take time on customization, you'll have to purchase 3 licenses for each URL, but we recommend you using one license with Categories module to distribute responses between them, but they will be visible to all members
I have a similar question. On Option 2, when you say that users can be assigned to specific categories, do they get to see only those ideas/questions...which have been tagged to the category? Is my understanding correct.
Also, will this restriction apply in all places, including the widget?
Thanks
Srini
I have a similar question. On Option 2, when you say that users can be assigned to specific categories, do they get to see only those ideas/questions...which have been tagged to the category? Is my understanding correct.
Also, will this restriction apply in all places, including the widget?
Thanks
Srini
Hello Sprini,
The categories are visible to everyone, but they could be private or public. The distribution of permissions could be done this way:
- One category you make private;
- Create new Role in Backend;
- Assign this Role to see private objects;
- Each users within this role will see responses, comments within this category, but also will see visible categories.
As of now this is the only option to support different customers within one community. But this can be extended with custom build modules, as system is modular. More information could be found at Developer Manual
Hello Sprini,
The categories are visible to everyone, but they could be private or public. The distribution of permissions could be done this way:
- One category you make private;
- Create new Role in Backend;
- Assign this Role to see private objects;
- Each users within this role will see responses, comments within this category, but also will see visible categories.
As of now this is the only option to support different customers within one community. But this can be extended with custom build modules, as system is modular. More information could be found at Developer Manual
Hi Stas,
I think this would be a great feature to have roles assigned to certain categories.
Please let me know how this could become available.
Thanks
Tim
Hi Stas,
I think this would be a great feature to have roles assigned to certain categories.
Please let me know how this could become available.
Thanks
Tim
Hi Tim,
As I can see it, categories module could be extended with choosing which role will be able to see it or not. It would take about 8-10 hours to extend it, but it's not something we can promise to incorporate by 1.2 release.
To distribute rights whether to see or not category could be done only with private objects module as of now but we'll think how it can be extended to not loose simplicity of the system
Hi Tim,
As I can see it, categories module could be extended with choosing which role will be able to see it or not. It would take about 8-10 hours to extend it, but it's not something we can promise to incorporate by 1.2 release.
To distribute rights whether to see or not category could be done only with private objects module as of now but we'll think how it can be extended to not loose simplicity of the system
Stas,
Have been waiting on this feature for sometime. I am bit apprehensive with work around solutions as in my case, the communities needs to be strictly separated and there should not even be an accidental access errors.
Srinivasan S
Stas,
Have been waiting on this feature for sometime. I am bit apprehensive with work around solutions as in my case, the communities needs to be strictly separated and there should not even be an accidental access errors.
Srinivasan S
Srinivasan,
Sorry, this feature is not on the roadmap till 3.0 release. This workflow will be considered, but not plans as of now.
P.S. Maybe as a part of ticketing system
Srinivasan,
Sorry, this feature is not on the roadmap till 3.0 release. This workflow will be considered, but not plans as of now.
P.S. Maybe as a part of ticketing system
Replies have been locked on this page!