tag:help.tenderapp.com,2008-11-12:/discussions/questions/13512-multiple-company-membershipTender: Discussion 2018-10-18T06:27:43Ztag:help.tenderapp.com,2008-11-12:Comment/376374902015-08-12T14:55:35Z2015-08-12T14:55:35ZMultiple company membership<div><p>Yes, a user may only be part of a single company so what you're
wanting to do wouldn't be possible.</p>
<p>Companies can be created via API - <a href="https://help.tenderapp.com/kb/api/companies">https://help.tenderapp.com/kb/api/companies</a>
- but users are assigned to the company via User API - <a href="https://help.tenderapp.com/kb/api/users">https://help.tenderapp.com/kb/api/users</a>.
Once they are assigned to a company they are a watcher on ALL
discussions belonging to ANY other member of that company and their
user profile settings control the notifications they would
receive.</p>
<p>Let us know if you have other questions.</p>
<p>Thanks,<br>
Nicole</p></div>Nicoletag:help.tenderapp.com,2008-11-12:Comment/376374902015-08-12T16:22:50Z2015-08-12T16:22:50ZMultiple company membership<div><blockquote>
<p>Yes, a user may only be part of a single company so what you're
wanting to do wouldn't be possible.</p>
</blockquote>
<p>That's too bad. It's a significant limitation from our
perspective.</p>
<blockquote>
<p>Companies can be created via API - <a href="https://help.tenderapp.com/kb/api/companies">https://help.tenderapp.com/kb/api/companies</a></p>
</blockquote>
<p>This document does not include how to create a company, only
getting a list and a single company. Am I to assume that including
a <code>Content-Type: application/json</code> header and a json
body with only the <code>name</code> param is how a company would
be created? Any other available params?</p>
<blockquote>
<p>but users are assigned to the company via User API - <a href="https://help.tenderapp.com/kb/api/users">https://help.tenderapp.com/kb/api/users</a>.</p>
</blockquote>
<p>While it is mentioned in the Companies API doc, the
<code>company_id</code> is not listed on the Users doc.</p>
<blockquote>
<p>Once they are assigned to a company they are a watcher on ALL
discussions belonging to ANY other member of that company and their
user profile settings control the notifications they would
receive.</p>
</blockquote>
<p>I think this is only true if the company's
<code>notifications_default</code> setting (undocumented) is
<code>true</code>.</p>
<p>So, I think the answer to my question is that the
<code>notifications_default</code> param set to <code>true</code>
instead of the default <code>false</code> is how this would be
achieved. Is that correct?</p></div>marctag:help.tenderapp.com,2008-11-12:Comment/376374902015-08-12T16:58:33Z2015-08-12T16:58:33ZMultiple company membership<div><p>Marc -</p>
<p>Sorry, while it's not documented, your basic POST to create a
new company will work. You can set the name and permalink_name,
though permalink_name will default to name if you don't sent a
value for it.</p>
<p>We mention it as company_name in the User docs and I'll make
that correction. I'll also add the notification_default setting to
Company docs as well. You are correct, if you set that to true then
users will receive notifications for all company discussions by
default, but each user can still turn notifications on or off on
their profile.</p>
<p>Thanks,<br>
Nicole</p></div>Nicoletag:help.tenderapp.com,2008-11-12:Comment/376374902015-08-12T17:42:48Z2015-08-12T17:42:48ZMultiple company membership<div><p>Hi Marc,</p>
<ul>
<li>if you're using SSO, you can create and/or assign a company
with the <code>company_name</code> parameter.</li>
<li>the permalink is not assignable over the api.</li>
<li>notifications_default should be defaulting to
<code>true</code></li>
<li>users can override the notification in their profile by setting
company notifications to 'off'. The override will only work if they
have no setting.</li>
</ul></div>Courtenaytag:help.tenderapp.com,2008-11-12:Comment/376374902015-08-14T15:50:01Z2015-08-14T15:50:01ZMultiple company membership<div><p>Thanks guys</p>
<blockquote>
<ul>
<li>if you're using SSO, you can create and/or assign a company
with the <code>company_name</code> parameter.</li>
</ul>
</blockquote>
<p>Sounds fragile. What if the company name changes? It would be
more reliable with <code>company_id</code> instead, right? On that
topic, a <code>company_external_id</code> would be quite
useful.</p>
<blockquote>
<p>The override will only work if they have no setting.</p>
</blockquote>
<p>I'm not sure I understand this.</p></div>marctag:help.tenderapp.com,2008-11-12:Comment/376374902015-08-19T17:28:35Z2015-08-19T17:28:35ZMultiple company membership<div><p>Well, you're being an architecture albatross now! :D</p>
<p>With SSO, it must be a one-shot payload that is always accepted,
so we accept company name to make it super simple. It's up to
"you", aka the service to keep a track of external IDs and tender
company IDs and names.</p>
<p>Users have a "nil" for company email preference by default. This
means they don't know/care. In this case it reverts to the
company's setting (notifications_default) which is generally "on".
If they manually enable the company mail, that's cool and will
actually override whatever the company settings are, but if they
then disable it, it's forced off, because now they're considered to
have a preference. Clear as mud!</p></div>Courtenay