Answers.Body: <p>I  think it is reasonable to give an organisation a Drupal account. After all, an organisation can also have an email address and a phone number. But I tried to create an organisation-Drupal account combination from the interface on a CiviCRM 4.7.15, but I did not succeed. I tried the following scenario.</p>
  
  <ul>
  <li>I created an organisation with an email address.</li>
  <li>I created a Drupal user with the same email address.</li>
  </ul>
  
  <p>Result: two contacts in CiviCRM, an Indiviual and an Organization.</p>
  
  <p>But under the hood, using SQL, you have more options.</p>
  
  <ul>
  <li>Insert or update the connection record in the table <code>civicrm_uf_match</code>.</li>
  <li>Update in SQL the type of a contact (the column is <code>contact_type</code>) from <em>Individual</em> to <em>Organization</em>.</li>
  </ul>
  
  <p>I tried this and the Contact View looks fine, and the record is not duplicated when I run the <em>synchronize users</em> job. This suggests that you can do this for a small set with some SQL manipulation, and for a large set you can create an extension.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-03T15:14:11.137Z
Answers.Text: If you don't have anyone comfortable implementing an SQL change like this for whatever reason I think you can set this up with views bulk operations and rules - but it's likely to be more difficult and time consuming than the more elegant solution posted above :)
Answers.UserDisplayName: Eli Lisseck
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-03T15:57:49.967Z
Answers.Text: Thank you for your solution. It solved my problem. But it looks weird that there is no solution except using SQL.
Answers.UserDisplayName: anis
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-03T16:11:24.650Z
Answers.Text: Hm, when someone logs in into the system, it is always a person. So there exists an individual, and from CiviCRM's point of view, it makes sense to register the details of this contact. And if this contact is related to an organisation, create a relationship. But I can imagine that if you combine this with CiviCase, it becomes complicated.
Answers.UserDisplayName: Kainuk - CiviCooP
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-04T12:29:33.307Z
Answers.Text: In general I think it is better to sync users with individuals. As you say a user has to be a person. An organisation can't log in. Only a person at the organisation can log in.
Answers.UserDisplayName: William Mortada
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-03T14:49:48.583Z
Answers.LastActivityDate: 2017-02-03T14:49:48.583Z
Answers.UserDisplayName: Kainuk - CiviCooP
Body: <p>I was trying to set contacts added by the synchronisation between Drupal users and CiviCRM contacts as an organisation contact not as an individual. But I can't find where to do so.
  Any suggestion? </p>
  
  <p>Thanks in advance.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-02-03T12:45:22.250Z
Comments.Text: i'm not sure you can Anis. It maybe useful to edit to your question to give a little more context and perhaps others can make suggests for other ways to achieve your goal.
Comments.UserDisplayName: ErichBSchulz
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-02-03T14:26:42.060Z
Comments.Text: Actually i need this because i am using civicase and i want to attach organisation contacts as roles in the case. That's why i want to create users where its contact type in CiviCRM is organisation not individual.
Comments.UserDisplayName: anis
Tags: <drupal>
Title: How to synchronise Drupal users with CiviCRM organisations
ThreadText: # How to synchronise Drupal users with CiviCRM organisations
  
  (Asked by: username_0 on 2017-02-03)
  
  I was trying to set contacts added by the synchronisation between Drupal users and CiviCRM contacts as an organisation contact not as an individual. But I can't find where to do so.
  Any suggestion?
  
  Thanks in advance.
  
  **Tags:** drupal
  
  > **Comments:**
  > **username_1**: i'm not sure you can username_0. It maybe useful to edit to your question to give a little more context and perhaps others can make suggests for other ways to achieve your goal.  
  > **username_0**: Actually i need this because i am using civicase and i want to attach organisation contacts as roles in the case. That's why i want to create users where its contact type in CiviCRM is organisation not individual.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2017-02-03. Score: 0 | Accepted answer
  
  I think it is reasonable to give an organisation a Drupal account. After all, an organisation can also have an email address and a phone number. But I tried to create an organisation-Drupal account combination from the interface on a CiviCRM 4.7.15, but I did not succeed. I tried the following scenario.
  
  * I created an organisation with an email address.
  * I created a Drupal user with the same email address.
  
  Result: two contacts in CiviCRM, an Indiviual and an Organization.
  
  But under the hood, using SQL, you have more options.
  
  * Insert or update the connection record in the table `civicrm_uf_match`.
  * Update in SQL the type of a contact (the column is `contact_type`) from *Individual* to *Organization*.
  
  I tried this and the Contact View looks fine, and the record is not duplicated when I run the *synchronize users* job. This suggests that you can do this for a small set with some SQL manipulation, and for a large set you can create an extension.
  
  > **Comments:**
  > **username_3**: If you don't have anyone comfortable implementing an SQL change like this for whatever reason I think you can set this up with views bulk operations and rules - but it's likely to be more difficult and time consuming than the more elegant solution posted above :)  
  > **username_0**: Thank you for your solution. It solved my problem. But it looks weird that there is no solution except using SQL.  
  > **username_2**: Hm, when someone logs in into the system, it is always a person. So there exists an individual, and from CiviCRM's point of view, it makes sense to register the details of this contact. And if this contact is related to an organisation, create a relationship. But I can imagine that if you combine this with CiviCase, it becomes complicated.  
  > **username_4**: In general I think it is better to sync users with individuals. As you say a user has to be a person. An organisation can't log in. Only a person at the organisation can log in.  
  
  ---
  
  