[OGo-Users] Default settings for new appointments, tasks, projects

[Adam Tauno Williams]

> > > I would like to change the default settings when a new appointment etc.
> > > is made. 
> > > Appointments: default is: read: private; write: not set
> > > Here I would like to have that all intranet can read by default.
> > You can set the default access rights for appointments in your
> > preferences. 
> Thank you. I can set write access rights but not read access. "Entries
> in popup of appointment overview" seem to have no effect (ogo 1.1.6).

The "Entries in popup of appointment overview" are effective for me.
These change the items listed in the drop down in the appointment
overview page (the default schedular page),  not when creating
appointments. At least in the default theme this is the select box in
the far upper left when looking at the schedular.  But default (with no
user default set this lists the current user and each of the systems
teams).

> > > Projects: 
> > > Here, the project basis is not defined. It would be nice for me to
> > > predefine "Database".
> > You can remove the filesystem backend for projects if you never want to
> > use it; and haven't already created filesystem projects.
> > >  Also nice would be to predefine the accounts.
> > For new projects?
> Yes. 
> > > I looked at /etc/opengroupware.org/NSDefault... etc. but could not find
> > > any settings which look like these.  
> > Check your preferences when logged into the WebUI.  Most of the Defaults
> > just apply to how the deamons operate.
> The only thing I could change in the preferences is the write access for
> appointments

Yes.  In part I suspect this is because setting the read access is a
simple singular-select while setting the write access is an [inherently]
more cumbersome multi-select.

> . There are too many clicks needed for many operations in
> ogo. If one could set more in the preferences, the usability of ogo
> would increase much, I think. Changes which seem not so complicated to
> me.

Please file enhancement requests for features who think are missing.
Default read access seems reasonable to me.  Not that the 

Aside: Personally,  I also see a flip side of allowing users to set
defaults for everything - they stop thinking about what options they
pick,  and then call the help desk ticked off when the application
doesn't psychically detect what they wanted it to actually do.