Home      FAQ      Forum      Idea Exchange      Ask a Question      My Stuff      Help   
  
Multi Location built into Team Desk Functions
Currently , I'm working on a "Locations" table whereby an employee is assigned to a location/business premise for the overseeing parent company ie "BIG COMPANY" has many "little locations/business sites" where all the people work!... This is great but what I'd really like TD to do is recognise the site a logged on "user" is at. With current functionality within TD, it is impossible(?).

What I propose is a new function that does two things - When an application is established, the new app owner can set up the Parent Company and the Sub Locations. They can then continue to invite users in the normal way and either assign a location to them right away or - even better - have the user, at the login screen, choose which location they're at...

The benefits of this are that a Sales person can be transfered from one location to another and create Leads/Quotes/Accounts etc for the location from which they are working from. The clunky way to do this at the moment is for the salesperson to *remember* to do this on every lead (Yes, I could make it a required field... I hear you say).
I just think this extra functionallity would be awesome in making TD a truely Multi Location, Multi Employee app...

Any suggestions very welcome
ID
415
Category
TeamDesk
Author

basenine
Date Created
1/28/2011 5:48:35 PM
Date Updated
1/29/2011 2:39:48 AM
Status
New Idea
Score
40
Promoted By
Nathan Phillips (CW)Philipp MatuschkaDesmond Beatty
basenine
Comments
basenine 1/28/2011 6:22:01 PM
Coupled With the "User" Functionality, this idea will make it easier to setup reports based on "Current User" ie, the lead can be assigned to a "User" instead of an employee from the "employee table"... The match conditions in a report could be for "Current User" - this means you only need to create one View/Report and the "Current User" will see their specific Leads/Quotes etc. when they're logged in. The Current way to do this requires me to setup a view with match conditions on each employee... Say I've got a hundred employees... Say they come and go (as employees do...)
Philipp Matuschka 1/29/2011 2:39:48 AM
As I said somewhere else, session variables ..... The idea here of setting those at the beginning of a session is really good
Feedback
 
Back to Search Results