ACS - Object Ownership and data safety

Hello All,

A few things related to ACS....

Point 1:

Is there any way to make created objects (i.e places, custom objects... anything) at a root level without having to use the appcelerator interface?

Senario 1: Multiple users use an app to create public points of interest (places), the user then stops using the service and deletes the account. All the points of interest that where created by the user also get deleted. The user created the POIs for the public domain?? Is there a way that the ACL can take ownership?

Senario 2: I want to bulk load 10,000+ places which is foundation of app. Currently has to be done using a user account (admin or regular). Say account gets deleted (these things happen) bang goes app!

Does this mean that I have to keep every user account created?

An isDeleted (true/false) custom field isn't really a manageable solution.

Could ownership be transfered to an admin account?

Is this a future feature - if yes how long?

Point 2:

Are ACL's supposed to bridge the gap between admin users and regular users?

Senario: Both admin user and regular user belong to same ACL with read/write permissions. Admin creates object, regular user want to update it. I cannot get this to work?

ACS is awesome and life is soooooo much easier with it, but compared to stack mob and other PaaS it just doesn't feel mature enough to run in production.

Last question(s) -say I lost my data by mistake - even if I have to pay is there a way to restore it? When will back up be available?

Even running just small time projects - my customers data and therefor my lively hood is on the line.

Many thanks,

IJ

Thanks for the feedback. for point 1, we will add a feature that you can transfer ownership of an object to a different user. We are continue working on to make ACS more flexible.