No for example we have a database and all objects are owned by user A but created by user S, and edited by many users U(n). The quota for all data in the tables owned by A is charged to user A. User A must grant the permission out the the users U for them to access them. Oracle does not keep track of the creating user just the schema owner. So if you have the create any table option and you create a table in different schema you will need to grant the creating user rights to the table before you can use it but the owner (created in schema) will have full rights to it right away.
This sounds like the approach we're starting to take, but I'm concerned about the fact that even though user S created the object, user A still has to supply the object privileges to users U and user S. Why do you keep user S in the process if they can only perform part of the necessary setup for a table? And how do you handle the logistics of the two step process of first creating the table and then supplying the rights? Are these actually two different users in your shop, or the same person with the knowledge of both passwords?
In our case user S is not really a user but the owner of the meta data of the data dictionary for the GIS system. User A is the Business user and again does not really refelect a user but more like a 'company.' The end users U are the ones that edit the data. Managers of the system have both the S and A password as both are needed to manager both the meta data and the business data. The managers log in as the user A to set permissions on the business data and log in as S to manage processes that impact the meta data.