Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

How to show different welcome screen based on Group access in AEM 6.3?

Avatar

Level 2

Hi

Recently we got requirement from client, Based on Group access we need to show different welcome screen in AEM 6.3

For example: If we have two groups "Classic-User-Group" and "Touch-User-Group"

If user belongs to touch UI group,We need to show only touch UI consoles,If user belongs classic, needs to show only classic ui consoles.

(Note: Should need to work with only groups, User is not ready to change the preference settings )

Thanks,

Sree

1 Accepted Solution

Avatar

Correct answer by
Level 10

Not possible OOTB but should be achieved by small piece of code.

You can add servlet and update root mapping, details can be found in summit session

https://github.com/Adobe-Marketing-Cloud/Summit2018/tree/L729/exercise1#3-dynamic-start-page

https://github.com/Adobe-Marketing-Cloud/Summit2018/blob/L729/code/L729/core/src/main/java/adobesumm...

View solution in original post

4 Replies

Avatar

Level 3

I think achieving this as a CMS customisation would be difficult and also applying the authoringMode at group level would be tricky.

I would probably do this as a Filter with an OSGI configuration where you could add the user groups that go to classic vs touch. The filter would redirect to /cf# or /editor.html for pages and to /siteadmin or /aem/start.html for the landing page.

Avatar

Correct answer by
Level 10

Not possible OOTB but should be achieved by small piece of code.

You can add servlet and update root mapping, details can be found in summit session

https://github.com/Adobe-Marketing-Cloud/Summit2018/tree/L729/exercise1#3-dynamic-start-page

https://github.com/Adobe-Marketing-Cloud/Summit2018/blob/L729/code/L729/core/src/main/java/adobesumm...

Avatar

Level 2

Thank You Arun for quick response,

I think filter would execute for every request, I will try with this solution.