Best Practices for Using Service Accounts with Data Connections

Folks, Is it a good practice that the service account used to connect Google drive, Notion and others also be an account existing in Dust? I am creating connections logged in to dust with my named account but using a service account to connect to services. Problem is there is no indication of the account being used when looking at the connection admin. And I'm also not sure about what happens if I for example have my named account deleted. For what I saw it is better to log in to dust with the service account and connect to data sources using the same account, but that also mean I need to be paying for a user that is not a builder... Can someone clarify?

10 comments

yutcam (Dust)
·
·
Hey Caio Zanolla! Are you using Dust for multiple teams or mainly for yourself and a few team members?
Caio Zanolla
·
·
For now I'm using it for a small team. Not clear yet if the whole team will use the same account or if we will split into multiple accounts. Actually, thats a good second question. I could not find any way to segregate teams inside one account. Any recommendation regarding this? Should we be creating different accounts for different teams? Our use case involves multiple bulders from multiple teams using the same sources of data
Caio Zanolla
·
·
yutcam (Dust) ping
yutcam (Dust)
·
·
Hey Caio Zanolla! I asked you this question because we have another plan for teams that would be better suited for your use. With this plan, you can segregate data into spaces. So, basically, if your plan is to use Dust for several teams, then I would recommend creating a service account and considering moving to a plan supporting SSO and data segregation in Spaces. You can read more about spaces here - https://docs.dust.tt/docs/data
Problem is there is no indication of the account being used when looking at the connection admin.
Could you elaborate on this? You should see the owner of the Connection once it is set up.
For what I saw it is better to log in to dust with the service account and connect to data sources using the same account, but that also mean I need to be paying for a user that is not a builder...
Yes, that's right, and we are changing this. We will create a service account role in Dust; this "user" won't be able to send any message and will be administrated by the admin as a regular user. You won't pay for this user. In the meantime, we can handle this manually and ensure we don't bill you for this account. It's also important that only Dust's admins can access the service account. Hope it helps!
Caio Zanolla
·
·
Thanks for the answers yutcam (Dust)
Caio Zanolla
·
·
regarding moving to some other plan, there is a huge gap between our current usage and the 100+ enterprise. Do you offer custom plans? lets say I have 10 people.
yutcam (Dust)
·
·
We have an intermediary plan we can enable manually. €39 per license From 1 user 1 month 150 messages/user/day Up to 1Gb/user 5MB (text embedded equivalent) Unlimited PDFs Okta & Entra ID included Up to 15 Spaces (restricted and unrestricted) Self-served Support via email
yutcam (Dust)
·
·
If you are interested, you can send an email to clement@dust.tt 🙂
Caio Zanolla
·
·
Giuseppe Ciotta 👆
yutcam (Dust)
·
·
🙇‍♀️