Re: Community approver not set in admin console but still required

beau.gordon@landesk.com — Wed, 05 Nov 2008 18:41:51 GMT

I guess removing John as the approver from SpaceA worked after all. It took a few minutes before he was removed as the approver for SpaceB.

Community approver not set in admin console but still required

beau.gordon@landesk.com — Wed, 05 Nov 2008 17:59:02 GMT

Hi,

Clearspace Community 2.0.8.

I created a new subcommunity named SpaceB beneath an existing community named SpaceA. SpaceA had a document approver configured named John. I didn't set up a document approver for SpaceB. When I try to create a new document in SpaceB, it requires John's approval.

That's OK if that is the intended design - I can see why you would want document approval settings to be inherited. Here are the problems I have:

1. If I remove John as the document approver for SpaceA, then new documents created in SpaceB still require his approval.

2. John isn't listed as the document approver for SpaceB inthe admin console, so I can't remove him.

Basically I don't want an approver for SpaceB but apparently I have no way of removing John as the approver.

Any ideas?

Thanks,

Beau

Jivespace: Message List - Community approver not set in admin console but still required

Re: Community approver not set in admin console but still required

Community approver not set in admin console but still required