nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

content type is visible to all the tenants in multi tenancy setup

skumar_us

Hi
I have created two tenants as customer1 and customer2 and deployed two custom models in each of the tenant repository using dynamic approach.

However the share config has the entry of all the content types for view purpose. Can share-custom-config xml be implemented specific to tenant ?
The content type for customer 1 and customer 2 is visible to both the tenant.
e.g. while uploading a document when clicked on content type it shows the content type of all the tenant.
We want our customer not to view each other content type. Is this can be possible in multitenancy setup.

Find more posts tagged with

Comments

afaust

Hello,

unfortunately, Alfresco Share does not provide a native configuration method to allow tenant-specific configuration. But with Surf extension module configuration it should be easy to set something up in that regards. Basically, all tenant specific configuration should go inside an extension module definition "configurations" section. That module would need to have an evaluator that checks the currently active tenant. That way, the tenant configuration is merged into the global configuration based on the current user / request context when the context relates to the tenant of choice.

Regards
Axel

mrogers

Dynamic models are tennant specific (certainly in 5.0 lfresco. I made it work efficiently 8-) and we use it for cloud.) So you should be able to configure Share with all types because they can then only show up in the appropriate tennant.

Config of alfresco Share has at least two teams working on it so there should be a different story soon.

afaust

Mark, relying on tenant-specific model surfacing only works for configuration that actually evaluates content types / existing nodes. But in Share we also have configuration that can't and would always show in all tenants, e.g. create content actions in document library or type/form selection drop down for advanced search. Those actions / features will fail at a later point in time due to missing types in tenants, but are nonetheless visible in the UI.
Looking forward to any tenant-aware out-of-the-box configuration features in the future…