Publish Later is not working for user groups where Deactivate later is working fine. | Community
Skip to main content
P
PoovithaSelvaraj
Level 3
March 2, 2023

Publish Later is not working for user groups where Deactivate later is working fine.

  • March 2, 2023
  • 2 replies
  • 1018 views

Hi , 

In my Project only particular user group is not able to Schedule Publish Later , Whenever user is triggering publish later , it is going to Request for Activation rather than Publish Later flow. 

He has read rights for all the nodes. 

Can someone suggest a way to fix this ?

 

Thanks in Advance, 

Poovitha S 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Rohit_Utreja
Community Advisor
Rohit_UtrejaCommunity Advisor
Community Advisor
March 2, 2023

@poovithaselvaraj 

Can you check if user has appropriate permissions to activate these pages?

'Request for activation' get triggered when user/group doesn't have replicate permissions.

 

I hope it helps.

    P
    PoovithaSelvarajAuthor
    Level 3
    March 3, 2023

    @rohit_utreja  he doesn't have replication rights, we want them to trigger to scheduled activation which takes to the similar workflow approvals and wait for the time of publish and then publish.

     

      SivakumarKanoori
      Community Advisor
      SivakumarKanooriCommunity Advisor
      Community Advisor
      March 2, 2023

      @poovithaselvaraj :

       

      Can you go to http://localhost:4502/useradmin

       

      and check the below option (Replicate column) has been checked or not for that user group.

       

       

      Thanks

      Siva

      Thanks,Siva
        P
        PoovithaSelvarajAuthor
        Level 3
        March 3, 2023

        Hi @sivakumarkanoori , 

        That user should have replication rights to apps, bin ? 
        We don't want that user have replication rights to /content and /content/dam but he should be able to trigger schedule later through Manage Publication right?

         

          Terms & ConditionsAccessibility statement

          Loading footer...