Smoke and mirrors.
@Tom-- can you elaborate a bit more on why you think this is smoke and mirrors?Thanks!
Umm - this is a great UI improvement, but what does it actually *do*? If the users from disabled orgunits are still coming across as fully authenticated and authorized, this just creates an illusion of administrative control, no?Maybe you can clarify what the back-end impact is, because as-is, this isn't really clear.
Think of this more as controlling the visibility of the app, with the main benefit is being able to disable (hide) the UI extensions of apps for groups of users. This is particularly important for gmail gadgets and was a frequently requested feature by users.For example, a lot of the CRM apps have gadgets that appear with *every* message in gmail. This is great for people in sales and support, but annoying for everyone else. Now admins can control the visibility of the extensions so only users who need the app will see it.
> New Scoping by Sub-organizationAs a Apps vendor with a comprehensive integration via Gmail gadget, SSO, etc. this feature offers MASSIVE value to us and our clients. A major constraint has been lifted allowing us to provide more features, automation and data context to those that really needed it.Thanks heaps for making this happen.
Are there any requirements to use this new feature? For example, does the application need to be using OAuth v2?I asked because we have noted that this feature works for our OAuth v2 application but not our AOuth v1 application.Thanks!
@David - no, there are not requirements such as the version of OAuth your app uses. Please help us understand what's working and what's not by posting over here: http://code.google.com/googleapps/support/marketplace/
Is it possible to block access (ie revoke auth) by an app for some of our org's users but enable it for others? We have a few sales folks that want to use Insightly but I don't want everyone's account to be accessible.
Post a Comment