21–29 of 29 posts
Earlier quoted context omitted.
It's a first-world problem that can take a lot of time. I'd much rather go to a single site and send out all of my invites than navigate to four individual sites and muck about in the settings to send an invite.
I can't see how inviting users to a handful of services could take longer than 5-10 minutes? Is that really a "lot of time"?
This looks like an interesting concept. How does it compare with LDAP/Active Directory/Google Apps integration?
I'm still trying to learn more about Active Directory everyday. Companies like Okta and OneLogin offer user provisioning (what Onboarder is doing) and they integrate with Active Directory. Onboarder is definitely not that complex yet, but I'm still learning about this space. My goal was to make it simple. Connect with OAuth or give us an API key, and we're good to go.
The onboarding/offboarding process is generally initiated from there, and internal apps and services tend to use that as the canonical user store.
Good luck with your project, I hope it works out well for you!
Hey everyone, I ran some Facebook ads and received some feedback from Reddit /r/startups. I decided it was enough validation to build it. If you're like me, you've probably used Basecamp, GitHub, Heroku, HipChat, and many other apps on a daily basis. One of the things I found annoying was sending out invitations to all of these different apps. Onboarder solves this. When you need to invite someone new, type in their…
I really don't mean to be a jerk, but this sounds like a terrible idea. Four places to send invites from? That's a first world problem, not a startup business opportunity.
This seems very valuable to large teams, and like a small convenience to large teams.
Earlier quoted context omitted.
It's a first-world problem that can take a lot of time. I'd much rather go to a single site and send out all of my invites than navigate to four individual sites and muck about in the settings to send an invite.
I can't see how inviting users to a handful of services could take longer than 5-10 minutes? Is that really a "lot of time"?
Another thing that would be awesome if your could get even finer grained control of some of the services. Like having the ability to maintain some additional Github permissions. A big pain point for us right now is you need to have admin to manage teams, webhooks, etc. Have some levels between admin and write would be great (and I don't blame GH for having these. It's a more enterprise need.)
Earlier quoted context omitted.
I really don't mean to be a jerk, but this sounds like a terrible idea. Four places to send invites from? That's a first world problem, not a startup business opportunity.
Companies routinely fail to disable access to users who no longer need it, creating security risks and increasing costs. This seems very valuable to large teams, and like a small convenience to large teams.
Hey everyone, I ran some Facebook ads and received some feedback from Reddit /r/startups. I decided it was enough validation to build it. If you're like me, you've probably used Basecamp, GitHub, Heroku, HipChat, and many other apps on a daily basis. One of the things I found annoying was sending out invitations to all of these different apps. Onboarder solves this. When you need to invite someone new, type in their…
I really don't mean to be a jerk, but this sounds like a terrible idea. Four places to send invites from? That's a first world problem, not a startup business opportunity.
Earlier quoted context omitted.
I really don't mean to be a jerk, but this sounds like a terrible idea. Four places to send invites from? That's a first world problem, not a startup business opportunity.
Companies routinely fail to disable access to users who no longer need it, creating security risks and increasing costs. This seems very valuable to large teams, and like a small convenience to large teams.