This does the trick. However, I happen to know that we also have some buggy redirect code that's supposed to redirect a single-organization user to the proposal list for that org, rather than the org list, when they first log in. Now, that code's all messed up at the moment - I don't think it works at all. Don't feel you have to go and fix that (unless you want to!) - it's on my list. My point though is this: we have two places in the code that defines what the first list view should be for an organization - it used to be proposals, now it should be discussions. Next time we change our minds about this (maybe we add a new type that comes before discussions) we'll have to remember to change those two places. I suggest therefore that  we centralise this somehow. It feels like it should be a method on the Organizations model, so that you could do org.get_list_url() (or org.get_list_url from a template) but that would be a pain to implement because it's a 3rd party library. A function somewhere in custom_organizations would be not quite as nice but certainly easier to implement, and certainly better than what we have now. You'd probably have to define a custom template filter to call it from the template (see https://docs.djangoproject.com/en/1.4/howto/custom-template-tags/#writing-custom-template-filters).