Recommended Way to setup a company owned Account and Databases

[PBK101]

I am currently setting up acompany account that  will be used to create and own all our databases. 

What is the recommended way of doing that ? 

Is there a way to  give admin/owner  access to more than one person ?  Is there a way to not create a shared owner account given  all the security issues that it entails. 

PBK

[Jacob Wenger]

Hey PBK,

I would suggest starting by creating a shared "slimmed down" Google account (not tied to Gmail, Google+, or any other Google service) for the company email address here. Use that Google account to log into Firebase.com and make it the owner of all of your Firebase apps. Use some mechanism to share that password with your entire team, or only those who need it.

You can then add personal Firebase accounts as collaborators from your account dashboard. Collaborators can do everything an owner can except managing members, managing billing, and deleting the Firebase app. Collaborators do have admin access to the Firebase app dashboards though which is probably what you want.

We do this internally and it works smoothly for us. It is a bit of a pain to share a common password for our shared account, but this will be getting better in the future.

Another option you can do is just have one person be the owner of your apps and have them control billing, app creation / deletion, and managing collaborators. Adding other team members as collaborators will grant them enough admin access to administer the apps otherwise.

Cheers,

Jacob

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/702f2d04-5481-41b2-8f48-5212c812c389%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[PBK101]

so if I want to use a shared account which we all agree I hope is a really really bad solution. I need to essentially create a new google apps account on our domain and pay $5 bucks a month for the privilege ?

Are you guys planning to improve this anytime soon ?

Pierre

[Jacob Wenger]

Hey there,

I offered an alternative solution to your problem in my last email:

Another option you can do is just have one person be the owner of your apps and have them control billing, app creation / deletion, and managing collaborators. Adding other team members as collaborators will grant them enough admin access to administer the apps otherwise.

To answer your other question: yes, this will be getting better in the future. We appreciate your patience.

Cheers,
Jacob

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/5449c0fe-aaea-4a52-a0c9-8ba4e348cdef%40googlegroups.com.

[Kato Richardson]

You don't need a google apps account and it doesn't need to be on your domain. You can use an existing team member's email address, or create a Google Account using any gmail/existing email address on any domain. Since it's purely going to be used as a login ID and for password recovery, it's not important that it be attached to your apps domain (unless you think this is important enough for $5/month).

We'll be adding more sophisticated team/group tools in the future. As always, we don't publish ballparks or release dates for upcoming features. This one is on the waiting list for future projects.

☼, Kato

To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAGcMwsDPOVi4PBRymZ2jiZKfAD7QnLO%3Da-X6mUr1Bde0v-qD%2BA%40mail.gmail.com.

[Rob Koberg]

On Thu, Jan 14, 2016 at 12:55 PM, Kato Richardson <wu...@firebase.com> wrote:
> <snip/>

>As always, we don't publish ballparks or release dates for upcoming features.
> This one is on the waiting list for future projects.
>

Any chance of seeing a list of what you guys are considering? Or at
least strongly considering?

[PBK101]

it is critical for such an account to be on a company domain because it allows to regain control through administration. Sharing a password among users is however seriously bad practice in terms of security. I hope you guys get team features on the very front burner