tag:help.lighthouseapp.com,2008-09-20:/discussions/suggestions/1812-organizational-api-tokenLighthouse: Discussion 2013-10-21T20:19:09Ztag:help.lighthouseapp.com,2008-09-20:Comment/265493212013-04-24T14:55:09Z2013-04-24T14:55:09ZOrganizational API token<div><p>Greg -</p>
<p>Since API tokens are unique to the user and basically act as
that users login, it is usually best practice that each person use
their own for other services. You could create a "group" user
profile and invite it as a member of your account to achieve what
you're talking about.</p>
<p>Thanks,<br>
Nicole</p></div>Nicoletag:help.lighthouseapp.com,2008-09-20:Comment/265493212013-04-24T15:05:31Z2013-04-24T15:05:31ZOrganizational API token<div><p>I can understand why you would want all ticket modifications to
be tied to a particular user, but that's not necessary for read
operations. For example, I was just working on a chat bot that
listens for Lighthouse links and responds with some basic ticket
information. Adding a dummy user for this purpose avoids the need
to change the bot's credentials if someone leaves, but it then
means that we have to manage a dummy user (which also means an
extra email address in our system).</p></div>Greg Pricetag:help.lighthouseapp.com,2008-09-20:Comment/265493212013-04-24T16:56:00Z2013-04-24T16:56:00ZOrganizational API token<div><p>Hi Greg,</p>
<p>If the use of the token is purely readonly, the owner can simply
generate a read-only one, and have everyone use it. Is that not
addressing your need? If so, can you explain a little more why?</p>
<p>If the bot has to take action, it makes sense to make the bot a
user, because actions on items need ownership. When users look at a
change, they want to know who and why, and it seems important to me
to know when a bot does something vs when a human does.</p>
<p>Let me know what you think.</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/265493212013-04-24T17:03:41Z2013-04-24T17:03:41ZOrganizational API token<div><p>The bot doesn't (and shouldn't) have an individual owner. If I
use my API token (as I have done thus far while writing and testing
the bot), then if/when I leave the organization, the bot will stop
working. If there were a read-only organizational token, then the
bot could continue to function no matter which individuals
left.</p></div>Greg Pricetag:help.lighthouseapp.com,2008-09-20:Comment/265493212013-04-24T17:12:30Z2013-04-24T17:12:30ZOrganizational API token<div><p>Yes, I get that, but the owner of an account is very unlikely to
change. Why not use a token generated by the owner in that
case?</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/265493212013-04-24T17:18:50Z2013-04-24T17:18:50ZOrganizational API token<div><p>Why do you think the owner is unlikely to change? The owner of
our account is just one of our PMs. He's not necessarily any less
likely to leave than any other individual in the organization. Even
if the account owner were less likely to leave, it just means that
we would run into the problem less often.</p></div>Greg Pricetag:help.lighthouseapp.com,2008-09-20:Comment/265493212013-04-24T17:31:13Z2013-04-24T17:31:13ZOrganizational API token<div><p>Well, in organizations, the head changes less often than the
individual members. Though clearly that is just my impression, and
an average, and can be wrong in particular cases.</p>
<p>I was also not opposing the fact that an organization token is a
good idea, simply trying to better understand your problem. I'll
create a ticket for this, but I can't really tell when it will
enter our development schedule, so for your particular account, I
would suggest going the "bot as a user" route (especially since you
have unlimited users). I know it involves managing one more email
address on your side, but this will definitely be the fastest
way.</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/265493212013-04-24T17:33:33Z2013-04-24T17:33:33ZOrganizational API token<div><p>Thanks. I didn't mean to sound so confrontational. We are
currently planning to go with the dummy user approach.</p></div>Greg Pricetag:help.lighthouseapp.com,2008-09-20:Comment/265493212013-04-24T17:40:43Z2013-04-24T17:40:43ZOrganizational API token<div><p>No worries. I'll close the discussion, but it will reopen when
we get to the ticket.</p>
<p>Cheers.</p></div>Julien