This should be read as:
After deletion of an SourceCast (not IZ) account this account 
shouldn't be reused,
because the underlying IZ account is disabled.

This is the way SourceCast behaves when IssueZilla is in 
single-database mode; that is, since IZ uses a single table for 
all project issues.

This probably will not get fixed, so I'm changing this as a task to 
document the behavior in the site documentation.

accepted

What is the recommended action for disabling access for a user then?
Disabling by setting a password which is unknown to the user?
Creation a role with no permissions?
And don't forget to disable the IZ account if you don't delete the
account.

The proper action should be to
1. Delete the SourceCast account, and
2. Disable the IZ account (with a comment in the disable box).

This will solve the situation.

Changing subcomponent.

Deleting the SC account and disabling the IZ accoubt would mean that
the SC account can be reused for registration of a new user. The new
user (with the old IZ id) would not be able to file issues.,
My understanding is that IZ accounts can't be deleted but we can only
disable them. This has to be reflected to SC accounts. We only can
disable them (by whatever means).

will work on this documentation this week. (sept 3) with a 
deadline of 10 Sept. Documentation will live in the 
documentation page. In addition to the 'deleted" accounts, must 
have something about the consequences of membership (which 
is why I have dallied on this).
louis

well, the deadline was surrendered more than a month ago, but I did it. added 
language to the effect that SC accounts can be deleted but IZ accounts only disabled. 
added this to project_issues.html. 

closing issue.
-louis

As agreed with Louis, we can close all the resolved fixed issues he owns.

As agreed with Louis, we can close all the resolved fixed issues he owns.