You can use Customize (M-x customize-group RET planner RET) to set user variables.
Other user options are:
If you really don't like day pages, you can set this variable to nil and you won't be prompted for dates for tasks (and notes, if using remember-planner).
If you really don't like plan pages, you can set this variable to nil and you won't be prompted for plan pages for tasks (and notes, if using remember-planner).
This variable controls what happens to files Planner opens by itself. If your tasks are associated with plan pages, the plan pages are updated whenever a task is rescheduled. This could lead to a lot of open buffers as Planner applies updates to all linked files. By default, Planner is configured to do nothing. A value of ‘save’ means save but do not close buffers, and a value of ‘nil’ means do not save any of the buffers.
This variable controls where new tasks are created. Non-nil means create tasks at the bottom of the first task block. If you set this to non-nil, new tasks will be listed in order of creation (oldest). Tasks carried over from previous days will appear at the bottom of the list.
Nil means create tasks at the top of the first task block. Carried-over tasks and newly created tasks are prominently placed on top of the list of tasks for the day.
Default page for created tasks. This is used as the initial value for tasks. After you create a task, it will be set to the previous page used.
Font-locking for tasks may be enough for you to determine status and priority. Set this to non-nil if you want to hide the status marker and rely on font-locking instead.
Functions run after creating a task.
planner-idhooks into this.
If non-nil, partial dates (ex: 2 or 5.2) are completed to dates in the future instead of using the current year and month.