From memory, the publisher sets the embargo date and time at the point that they approve the workflow. So author creates, requests publication, and publisher looks at the workflow tab when they get the request. I'm sure it's on there.

Mark

The embargo is edited on the workflow at the time of publishing, so a change has to be requested to be published. An administrator can't do this directly. You'll need to set up an author role, an authors group that uses that role, and add an author user to the group. Then on sitetree, change the permissions so that authors can edit all pages, and administrators can publish.

Mark

As at RC4, I think the Request Publication button is present, even for administrators. So to do what you want, as an admin you can request publication of a change you make, which will give you a workflow request.

I committed a change to trunk of cmsworkflow (earlier today in fact) that removes the request publication button from administrators and publishers. This was filed as a ticket on open.silverstripe.org, as a bug. It would appear that different people want to use workflow differently (some people want to bypass it, some don't), so it probably should be an option if you want that behaviour or not. I may revert the change to trunk (it won't effect whats in RC4 that you have installed), and see if a better solution can be found for the 1.0 final that provides the flexibility.

Mark

Ok, so you're just using the module for embargo only. There is a simpler module called embargoexpiry ([[http://silverstripe.org/embargo-expiry-module/]]). Version 0.2.2 is supposed to work with 2.4, although I haven't used that personally. I think the intention is that cmsworkflow will replace embargoexpiry, but the latter should work for you now. cmsworkflow comes from a different, more complex set of use cases, of which embargo and expiry is just one. But we may have a little work to do to make it work for the simpler use case out of the box.

Mark