How to give everyone the global view by default?

[SylviaE]

Hi folks,

We are just evaluating sugar and one question we could not answer yet is: How do you give by default every user the global view? We want all our users to see all information about all our customers/contacts. We do not want to filter. If I enter a new account and contact then all my colleagues need to be able to see them.

What we tried so far was we removed the private teams and only have the global team and the admin. So when someone enters a new contact or account etc. then they only can set it on "global",

That addresses the problem but creates a new one:

When a user enters a contact and forgets to set this global then the contact completely disappers for that user and only the admin can recover it.

Question:
Is there a better way to do this?
Or - if you use the global team parameter - can this somehow be set "default" for all modules?

Thank you! - Sylvia

[Angel]

There are a few ways to address this, but all require a slight bit of custom code.

The first (and preferred) method would be to use the logic hooks functionality to automatically assign the global team name to anything that is entered. That would be the preferred method because it is upgrade safe.

A second method would involve modifying the Sugar code and hard coding the global team identifier everywhere.

A third option would be to do it through some automated routine on the SQL server.

[paragontrailer]

So how do you use this "logic hooks functionality" and why is everything in SugarCRM a code modification? I would think Sugar would be much better accepted and marketable if there were certain wizards used to modify some functinality within the system.

[Angel]

So how do you use this "logic hooks functionality" and why is everything in SugarCRM a code modification? I would think Sugar would be much better accepted and marketable if there were certain wizards used to modify some functinality within the system.

Those wizards do exist, mostly in the form of the Studio.

It is impossible for it to do everything everyone wants, especially with a nice interface on top of it. The only time you need to make a code modification is when you want to do something outside the boundaries of built in functionality. That's true for any piece of software. Presenting code modifications as though they were a universal requirement in the Sugar world is an erroneous argument.

In the Sugar world, I at least have the option of adding features that aren't already there, or changing the behavior of existing ones. Try doing that with ACT!, Sage, Salesforce or MS CRM. That's the differentiator between Sugar and the rest of the packages. All packages have customization capabilities, but they also all their limits to what can be customized. In Sugar, I can extend them further by doing some of the coding myself.

That being said, you also have to keep in mind that it is a maturing product. Other features/wizards will come into being as time goes on.

As for the logic hooks, there is documentation on them in the Wiki, here is a link to an article discussing the matter at hand: http://www.sugarcrm.com/wiki/index.p...l_custom_logic