Start Here: Difference between revisions

From Accelerator for SageCRM
No edit summary
No edit summary
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
We have 2 Outlook clients now.
1. New UI - on this page
2. Classic - start here [https://accelerator.crmtogether.com/index.php?title=Outlook_Structure Outlook Structure]
-----
Client requirements for the new Client is that CRM must be on SSL. This means that you CRM must be using "https".
EG
  https://crm.yourserver.com/crm/eware.dll
You can buy a cert from an authority or use something like [https://letsencrypt.org/ https://letsencrypt.org/] to create a free cert.
-----
If you are a Sage CRM partner or customer of CRM Together you can download the server software from our portal at
If you are a Sage CRM partner or customer of CRM Together you can download the server software from our portal at


   [https://crm.crmtogether.com/customer365/logon.aspx Customer365 Portal]
   [https://crm.crmtogether.com/customer365/logon.aspx Customer365 Portal]


You need to already be a registered partner or customer to access this. Please contact us from crmtogether.com if you cannot get access.  
You need to already be a registered partner or customer to access this. Please contact us from https://crmtogether.com/contact/ if you cannot get access.  


The client software downlaod link will be available in Sage CRM once the server side is installed but is hosted at  
The client software download link will be available in Sage CRM once the server-side is installed but is hosted at  


   [https://update.crmtogether.com update.crmtogether.com]  
   [https://update.crmtogether.com?utm_source=achelp&utm_medium=link&utm_campaign=helplink update.crmtogether.com]  


and once installed updates are flagged automatically in the client application. You do not need administrator privilege's to install the software.  
and once installed updates are flagged automatically in the client application. You do not need (and should not use) administrator privilege's to install the client software.  


The Office 365 install uses the url
The Office 365 manifest install uses the URL


   [https://update.crmtogether.com/acmanifest.xml Office365 Manifest]
Version 5.2
   [https://update.crmtogether.com/version1260-manifest.xml Office365 Manifest AC 5.2]


to load in the application. This can be installed per user or via the admin area and users given access as required.
to load in the application. This can be installed per-user or via the admin area and users are given access as required. This is done via the 365 interface. Check out microsofts latest documentation to see how to do this.


Watch [https://vimeo.com/547526467 here]
Watch [https://vimeo.com/547526467 here]
[[File:office365install.png]]
 
to see it in action
to see how a user can do this.
 
NOTE: If your CRM URLS map to a private IP address when users are on your network this will cause a COR's issue. Your CRM URLS must always map to your public IP even if the user is on the network.

Latest revision as of 22:02, 3 March 2023

If you are a Sage CRM partner or customer of CRM Together you can download the server software from our portal at

 Customer365 Portal

You need to already be a registered partner or customer to access this. Please contact us from https://crmtogether.com/contact/ if you cannot get access.

The client software download link will be available in Sage CRM once the server-side is installed but is hosted at

 update.crmtogether.com 

and once installed updates are flagged automatically in the client application. You do not need (and should not use) administrator privilege's to install the client software.

The Office 365 manifest install uses the URL

Version 5.2

 Office365 Manifest AC 5.2

to load in the application. This can be installed per-user or via the admin area and users are given access as required. This is done via the 365 interface. Check out microsofts latest documentation to see how to do this.

Watch here

to see how a user can do this.

NOTE: If your CRM URLS map to a private IP address when users are on your network this will cause a COR's issue. Your CRM URLS must always map to your public IP even if the user is on the network.