"Owner" Pseudo Role - any insights?

[kpritchard]

I'm trying to figure out the relationship between the pseudo role "Owner" of a WTDocument and the creator of the WTDocument. Is the creator the "Owner" bydefault?

End Goal: I'd like to be able to extend almost Administrative (no Set State) permissions to WTDocuments that have not been "Released" previously. (I've added"New" and initial Lifecycle State). Workflows have a "Creator" pseudo role, but the ACL does not appear to. I coulduse "teamMembers", but then in a worst case member A could then delete member B's work.

Any insights are greatly appreciated

[ddemay]

By default on many objects, they are initially the same unless a
customization changes them or in due time, the owner becomes someone else
while a record of the creator remain intact. If you really were going to do
team members, adding a different unique role would be a safer IMO.